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

Cloud computing history

For our purposes, the first age of computing was the 1970s when the focus was on big infrastructure. Green-screen terminals, in vogue back then, eventually evolved into personal computers. Networks went from a centralized, hierarchical design to a decentralized design. Decentralization moved the processing closer to the user meaning applications moved from thin client (processing on the server) to thick client (processing on the user/client side). Green screens were tightly coupled interfaces to the data-laden backend. Decentralization enabled developers to track process steps and state information on the server side while allowing client-side computers to do much more of the processing. The period was the birth of client-server architectures, which are central to today's modern technology-driven business.

With much of the processing moving closer...