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
Foreword
Contributors
Preface
Index

Application centric design (CNMM Axis-2)


In the previous section, we saw some of the key cloud-native services that AWS has to offer. Now, in this section, we will look at the second axis of CNMM on how to create AWS native architectures. Although there are multiple different architectures and approaches, we will focus on two key patterns – serverless and microservices. In fact, these two patterns are related as well since the services that help us create a serverless pattern are also applicable to creating smaller, single functionality, fine-grained services in a system. So, let's explore more about how to create a microservice that is also serverless in nature in the next section.

Serverless microservice

The core concept around a serverless microservice is a three-step pipeline, such as the one shown in the following diagram:

Three-step pipeline

Let's discuss these steps in detail.

API trigger

The microservice can be invoked in two ways as follows:

  • An end user who's directly interacting with...