Data Architecture for Software Architects

Chapter 5. Architecting data in motion

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 8th chapter of the final book. Please note that the GitHub repo will be made active later on.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at [e-mail].

In earlier chapters, we focused on how data is structured, stored, once it comes to rest. But modern systems rarely operate in isolation, they are integrated with various systems that provide them data or data needs to be provided to them. Prices change in response to demand, inventory updates ripple across regions, and customer interactions generate signals that must be acted on in near real time. In this world, data is constantly moving, and its value is tightly bound to when and how reliably it arrives.

Architecting for data in motion requires a different mindset as compared to data at rest. It is no longer enough to model data correctly; we must ensure that data flows predictably across systems, that failures are visible rather than silent, and that downstream consumers can understand and trust what they receive. The challenge is not just moving data quickly, but moving it with confidence using APIs, events, streams, and files that span organizational ...