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
1
Prologue
18
Hands-On Lab 1 – Basic Cloud Design (Single Server)
20
Hands-On Lab 3 – Optimizing Current State (12 Months Later)
21
Cloud Architecture – Lessons Learned
22
Epilogue

Foundation for design – the cloud is economic, not technical

Contrary to what most believe, the cloud is not a technological innovation; it is an economic one. Although the cloud is based on virtualization technology, virtualization is not a new technology. Virtualization has been around for more than 50 years, starting with IBM mainframes in the early 60s, namely the CP-40. For decades, we have been trying to match better hardware and system utilization to the task or workload we are working to complete. Virtualization started with scientists and mathematicians from both IBM labs and MIT trying to perform complex calculations. They were trying to get more work done and, at the time, one task was limited to one system. IBM came up with the idea of virtualizing memory, which creates separate instances and completing more tasks could take place in the same amount of time...