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

Key performance indicators


A focus on the mean time to recovery is critical to achieving the promise of cloud-native. The traditional focus on maximizing the mean time between failures is too conservative a posture for companies to thrive in this day and age. Companies must be lean, move fast, experiment, and pivot quickly. We must be willing to make mistakes and rapidly adapt. Fortunately, the cloud-native concepts that empower teams to rapidly deliver innovation also empower them to rapidly repair and roll-forward. Yet, in order to make a repair, we must first identify the need for a repair.

We are already confident in our ability to move fast. We have spent the vast majority of this book on the topic. However, to be truly confident in the pace of cloud-native, we must be confident that we will detect problems in our cloud-native systems before our users do. When our customers do find the need to report a problem, we want the support team to be able to inform the customer that the solution...