Book Image

Cloud Native Development Patterns and Best Practices

By : John Gilbert
Book Image

Cloud Native Development Patterns and Best Practices

By: John Gilbert

Overview of this book

Build systems that leverage the benefits of the cloud and applications faster than ever before with cloud-native development. This book focuses on architectural patterns for building highly scalable cloud-native systems. You will learn how the combination of cloud, reactive principles, devops, and automation enable teams to continuously deliver innovation with confidence. Begin by learning the core concepts that make these systems unique. You will explore foundational patterns that turn your database inside out to achieve massive scalability with cloud-native databases. You will also learn how to continuously deliver production code with confidence by shifting deployment and testing all the way to the left and implementing continuous observability in production. There's more—you will also learn how to strangle your monolith and design an evolving cloud-native system. By the end of the book, you will have the ability to create modern cloud-native systems.
Table of Contents (12 chapters)

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...