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

Saga


Trigger compensating transactions to undo changes in a multi-step flow when business rules are violated downstream.

Context, problem, and forces

You are building a reactive, cloud-native system that is composed of bounded isolated components. You employ the Cloud Native Databases Per Component and Event Streaming patterns as the backbone of the system. You atomically produce events based on the Database-First variant of the Event Sourcing pattern and you leverage the CQRS pattern to isolate components from upstream failures and make them responsive, resilient, and elastic. You implement business processes based on the Event Collaboration and/or Event Orchestration patterns. The Data Lake pattern provides a system-wide audit trail of all events emitted by the system and, following the Stream Circuit Breaker pattern, your stream processors properly handle technical failures.

The Event Collaboration and Event Orchestration patterns provide the ability to leverage asynchronous inter-component...