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

Trilateral API per container


In the Trilateral API pattern in Chapter 3, Foundation Patterns, we talked about how a cloud-native component can publish up to three different interfaces: a synchronous API for processing commands and queries, an asynchronous API for publishing events as the state of the component changes, and an asynchronous API for consuming the events emitted by other components. The synchronous API is usually published via the API Gateway pattern, as discussed in Chapter 4, Boundary Patterns. The asynchronous API for consuming events is usually implemented as a stream consumer, as discussed in the Event Streaming pattern and the asynchronous API for publishing events is usually implemented as a database stream consumer following the Database-First variant of the Event Sourcing pattern, as discussed in Chapter 3, Foundation Patterns. This means that a cloud-native component will also consist of multiple deployment units.

Containers are very important in cloud-native systems...