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

Summary


In this chapter, we discussed the boundary patterns of reactive, cloud-native systems. Although we focus on asynchronous, event-driven inter-component communication, we ultimately need to implement synchronous communication at the boundaries where the system interacts with humans and external systems. The API Gateway pattern provides a secure and scalable foundation for synchronous communication. With the CQRS pattern, we leverage materialized views to decouple upstream dependencies in order to make the synchronous communication responsive, resilient, and elastic. The offline-first database pattern allows some synchronous interactions to operate locally by storing event and materialized view data in local storage and synchronizing with the cloud to increase the availability of the system from the user's perspective. The BFF is a higher-order pattern that pulls all these patterns together to create dedicated and self-sufficient components, which provide synchronous system boundaries...