Book Image

Architecting Cloud Native Applications

By : Kamal Arora, Erik Farr, John Gilbert, Piyum Zonooz
Book Image

Architecting Cloud Native Applications

By: Kamal Arora, Erik Farr, John Gilbert, Piyum Zonooz

Overview of this book

Cloud computing has proven to be the most revolutionary IT development since virtualization. Cloud native architectures give you the benefit of more flexibility over legacy systems. This Learning Path teaches you everything you need to know for designing industry-grade cloud applications and efficiently migrating your business to the cloud. It begins by exploring the basic patterns that turn your database inside out to achieve massive scalability. You’ll learn how to develop cloud native architectures using microservices and serverless computing as your design principles. Then, you’ll explore ways to continuously deliver production code by implementing continuous observability in production. In the concluding chapters, you’ll learn about various public cloud architectures ranging from AWS and Azure to the Google Cloud Platform, and understand the future trends and expectations of cloud providers. By the end of this Learning Path, you’ll have learned the techniques to adopt cloud native architectures that meet your business requirements. This Learning Path includes content from the following Packt products: • Cloud Native Development Patterns and Best Practices by John Gilbert • Cloud Native Architectures by Erik Farr et al.
Table of Contents (24 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Command Query Responsibility Segregation (CQRS)


Consume state change events from upstream components and maintain materialized views that support queries used within a component.

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 responsiveness because of the additional overhead required to traverse the...