Book Image

Architecting Cloud Computing Solutions

By : Kevin L. Jackson, Goessling
Book Image

Architecting Cloud Computing Solutions

By: Kevin L. Jackson, 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

Architecture Executive Decisions

The cloud is changing everything. Change occurs every day in the cloud services market. Changes to solutions, services, pricing models, consumption models, and locations all lead to different strategies, technology choices, economic impacts, and risk profiles.

Today, it is a normal process for the consumer to express what solution and solution components they require in the form of an RFI, RFP, RFQ, or some other type of requirements document, emailing a spreadsheet, for example. The consumer expresses what their experts need based on a mix of data sources, including business requirements, current state information, and the latest innovative articles read by a partially involved IT leader. Requirements are sent to one or more providers with the providers expected to respond to what is requested. Pricing is normally added and the response returned...