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

CapEx versus OpEx

When building the business case for cloud, one of the most compelling arguments to senior leadership (read: C-suite) is the ability to shift IT spending from Capital Expenditures (CapEx) to Operational Expenditures (OpEx). A capital expense is defined as money spent by a business on acquiring or maintaining fixed assets, such as land, buildings, and equipment. An operating expense is defined as the ongoing cost for running a business/system or providing a service/product.

There are several advantages that make up a compelling business case for leaders to transition to an OpEx model, which are enumerated as follows:

  • Lower, recurring costs versus large, upfront investments: As mentioned earlier in this chapter, building out a data center requires large amounts of time and resources to bring the compute power online. The cost associated with the time and resource allocation to building a data center is large. In an OpEx model, the business can achieve the same end result without...