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

Cloud economics

In many companies, a central IT organization manages infrastructure and charges back the price of IT services vended to the lines of business (LOB) plus their own administrative costs (known as a chargeback model). It is important to realize that the chargeback price rarely equals the price of cloud (for an equivalent stack). In these pricing exercises, rarely do central IT organizations take into account facility costs, security, cooling, water, and electric in their prices.

The price of a cloud stack must be compared to the chargeback price plus capital expenditures (building and equipment), operational expenditures (electricity, cooling, water), staffing, licensing (costs for virtualization software, ISV/third-party tools, and so on), facilities, overhead, and opportunity costs. This is referred to as Total Cost of Ownership, or TCO. Azure ( and AWS ( have TCO calculators that allow users to make reasonable numerical...