Part II. Putting Things Back Together
Attempting to divide a cohesive module would only result in increased coupling and decreased readability.
Larry Constantine
Once a system is broken apart, architects often find it necessary to stitch it back together to make it work as one cohesive unit. As Larry Constantine so eloquently infers in the preceding quote, it’s not quite as easy as it sounds, with lots of trade-offs involved when breaking things apart.
In this second part of this book, we discuss various techniques for overcoming some of the hard challenges associated with distributed architectures, including managing service communication, contracts, distributed workflows, distributed transactions, data ownership, data access, and analytical data.
Part I was about structure; Part II is about communication. Once an architect understands the structure and the decisions that lead to it, it’s time to think about how the structural parts interact with each other.
Get Software Architecture: The Hard Parts now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
