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

Defense in depth


Security and redundancy go hand in hand. Each layer of the system architecture has its own fortification. This redundancy ensures that if an outer layer is breached, then the next layer can potentially thwart the attack or at least slow it down long enough for the initial breach to be repaired. The number of layers in our cloud-native components is purposefully shallow. All inter-component communication is performed asynchronously via event streaming and all synchronous intra-component communication is with highly available, value-added cloud services, such as cloud-native databases. Our boundary components, such as a BFF component, have the most layers with an edge layer, a component layer, and a data layer; whereas fully asynchronous components will not have an edge layer, because they are entirely internal. The following diagram summarizes the topics we will discuss at the different layers:

Edge layer

We touched on the importance of leveraging the edge of the cloud in the...