Book Image

Architecting Cloud Native Applications

By : Kamal Arora, Erik Farr, John Gilbert, Piyum Zonooz
Book Image

Architecting Cloud Native Applications

By: Kamal Arora, Erik Farr, John Gilbert, 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. This Learning Path teaches you everything you need to know for designing industry-grade cloud applications and efficiently migrating your business to the cloud. It begins by exploring the basic patterns that turn your database inside out to achieve massive scalability. You’ll learn how to develop cloud native architectures using microservices and serverless computing as your design principles. Then, you’ll explore ways to continuously deliver production code by implementing continuous observability in production. In the concluding chapters, you’ll learn about various public cloud architectures ranging from AWS and Azure to the Google Cloud Platform, and understand the future trends and expectations of cloud providers. By the end of this Learning Path, you’ll have learned the techniques to adopt cloud native architectures that meet your business requirements. This Learning Path includes content from the following Packt products: • Cloud Native Development Patterns and Best Practices by John Gilbert • Cloud Native Architectures by Erik Farr et al.
Table of Contents (24 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

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 (https://www.tco.microsoft.com/) and AWS (https://awstcocalculator.com/) have TCO calculators that allow users to make reasonable numerical...