Context, problem, and forces
You are building a reactive, cloud-native system that is composed of bounded isolated components. Each component leverages value-added cloud services to implement one or more cloud-native databases that are exclusively owned by each component. This isolation empowers your self-sufficient, full-stack team to rapidly and continuously deliver innovation with confidence.
This isolation also makes it challenging to work with data across components. First, making synchronous requests between components to retrieve data is problematic. Second, making multiple synchronous requests to retrieve and join data from multiple components is even more problematic. Inter-component synchronous requests increase latency and reduce ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access