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

Focus on recovery


We have accepted the reality that to err is human and that our bounded isolated components will inevitably experience failures. We will instead focus our energies on the mean time to recovery. We have instrumented our components to be highly observable and we have strategically created synthetic transactions that continuously generate traffic through the system so that we can observe the behavior of key performance indicators. We have created alerts that monitor the key performance indicators, so that we can jump into action as soon as a problem is detected. From here we need a method for investigating the problem and diagnosing the root cause that allows us to focus our attention and recover as quickly as possible.

Teams should create a dashboard for each component in advance. A dashboard should display all the work metrics for a component and the metrics for the resources it consumes. All events should be overlaid on the dashboard as well. Note that it is the grouping...