Cloud Application Architecture Patterns

Chapter 6. Event-Driven Architecture

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 6th chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

A recurring theme for evolving an application architecture is to encapsulate components and decouple them. One motivation for identifying modules in a Modular Monolith is to reduce the coupling between cohesive units of code in the same application. Likewise,Distributed Architecture decouples modules further into services so that they can run on separate computers. Microservice Architecture decouples services even more into Microservices so that they can be developed and deployed independently.

Loose coupling facilitates disassembling an application into independent components by minimizing the dependencies of each component on the implementations of other components that it uses. A Service API decouples a service consumer from a service provider, so much so that when one service provider is replaced by another with the same service interface and similar functionality, the overall application still functions correctly. The service interface hides changes ...