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

Example – end-to-end relay


Let's pull this all together with an end-to-end example of a typical ordering process of an e-commerce system. At the highest level, the system receives an order, forwards the order to a third-party order-management system, and receives order status updates. The system is built using our cloud-native patterns.

We have a frontend (FE) application that submits orders to its BFF component. The BFF component emits the order-submitted event type and consumes the order-received and order-fulfilled event types to track the order status. These two pieces are owned by the same team. Another team owns the external service gateway (ESG) component that encapsulates the interactions with the third-party order management system. This component consumes the fulfill-order event type and emits fulfill-order-received and fulfill-order-complete event types. A third team owns the order process event orchestration component (EO) that is responsible for orchestrating the events between...