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

Service-oriented architectures and microservices

The origin of cloud development for the leading CSPs stems from the pain of managing monolithic systems. As each company ( retail site,'s indexing of the web) was experiencing tremendous growth, the traditional IT systems were incapable of keeping up with the rate of expansion and evolving at a necessary pace to enable the innovation that was needed. This story is true and well-documented in the public sphere for both AWS and GCP. As their internal systems matured around these services (provided initially as internal only to product development teams), Amazon took the step to provide these services to external customers on a utility-based billing system.

Many businesses and architects now see the virtue in this decoupling process, calling the fully decoupled environment a service-oriented architecture (SOA). We define SOAs as digital environments where each constituent system providing the lowest level of application functionality...