Book Image

Cloud Native Architectures

By : Tom Laszewski, Kamal Arora, Erik Farr, Piyum Zonooz
Book Image

Cloud Native Architectures

By: Tom Laszewski, Kamal Arora, Erik Farr, 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. To harness this, businesses need to refresh their development models and architectures when they find they don’t port to the cloud. Cloud Native Architectures demonstrates three essential components of deploying modern cloud native architectures: organizational transformation, deployment modernization, and cloud native architecture patterns. This book starts with a quick introduction to cloud native architectures that are used as a base to define and explain what cloud native architecture is and is not. You will learn what a cloud adoption framework looks like and develop cloud native architectures using microservices and serverless computing as design principles. You’ll then explore the major pillars of cloud native design including scalability, cost optimization, security, and ways to achieve operational excellence. In the concluding chapters, you will also learn about various public cloud architectures ranging from AWS and Azure to the Google Cloud Platform. By the end of this book, you will have learned the techniques to adopt cloud native architectures that meet your business requirements. You will also understand the future trends and expectations of cloud providers.
Table of Contents (19 chapters)
Title Page
Packt Upsell

The cloud native way

In the earlier chapters, we disassembled the monolith through decoupled, highly available architectures composed of microservices. These services were built in such a way that they could be managed and evolved independently of other components of a system. The technological services underpinning these microservices progressed rapidly, but the organizations that built these systems remained monolithic.


Through painstaking and patient experimentation, companies such as Amazon found that the best way to build systems powered by decoupled microservices was with decoupled micro teams. These teams are the personification of microservice architectures: small, decoupled, and autonomous. Amazon calls these teams two-pizza teams, since the whole team can be fed with two pizzas. We will refer to these as CND teams.

Each CND team comprises all the talent and skills required and the owners needed to design, build, deliver, and operate a service. They are a self-contained organizational...