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)

Accounts as code

Before we can build and deploy our cloud-native components we need to build and deploy the cloud accounts that they will run in. Far too often insufficient attention is paid to the architecture of cloud accounts. As we discussed in Chapter 2, The Anatomy of Cloud Native Systems, there is a great deal of thought that needs to put into the design of cloud accounts to ensure proper bulkheads. We certainly need to have separate accounts for production and development. In production, components could be spread across multiple accounts, such as separate accounts for front-office and back-office components. To support regulatory compliance, while also minimizing the scope of compliance, we may isolate certain components with higher sensitivity to their own accounts with additional access restrictions and procedures. A master account for consolidated billing is always...