Book Image

Architecting Cloud Computing Solutions

By : Kevin L. Jackson, Scott Goessling
Book Image

Architecting Cloud Computing Solutions

By: Kevin L. Jackson, Scott Goessling

Overview of this book

Cloud adoption is a core component of digital transformation. Scaling the IT environment, making it resilient, and reducing costs are what organizations want. Architecting Cloud Computing Solutions presents and explains critical cloud solution design considerations and technology decisions required to be made for deploying the right cloud service and deployment models, based on your business and technology service requirements. This book starts with the fundamentals of cloud computing and its architectural concepts. It then walks you through cloud service models (IaaS, PaaS, and SaaS), deployment models (public, private, community, and hybrid) and implementation options (enterprise, MSP, and CSP) to explain and describe the key considerations and challenges organizations face during cloud migration. Later, this book delves into how to leverage DevOps, Cloud-Native, and serverless architectures in your cloud environment and presents industry best practices for scaling your cloud environment. Finally, this book addresses in depth how to manage essential cloud technology service components, such as data storage, security controls, and disaster recovery. By the end of this book, you will have mastered all the design considerations and operational trades required to adopt cloud services, no matter which cloud service provider you choose.
Table of Contents (24 chapters)
Free Chapter
Hands-On Lab 1 – Basic Cloud Design (Single Server)
Hands-On Lab 3 – Optimizing Current State (12 Months Later)
Cloud Architecture – Lessons Learned

Technical architecture requirements

Cloud computing services are consumed using an on-demand model. Service providers, therefore, meter and monitor the consumption of every resource by every user. Every resource, in turn, uses specific metrics and measurement units to bill users. Most organizations do not measure IT usage in this way. Neither do they typically place resource measurement sensors across their IT platform. IT is usually seen as a shared cost center with only the total cost and total capacity requirements tracked. This makes it extremely difficult to estimate service usage rates and expected cost when an application is transitioned to a CSP. Infrastructure analysis is used to get estimates of resource usage by particular applications, business processes, and organizational segments. This is normally one of the most difficult aspects of developing the business case...