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

Cloud computing clients

Native applications are built and designed for specific mobile devices. They install directly on the hardware after being downloaded from app stores or marketplaces. These applications are designed to be compatible with native features of the target device hardware and can work as standalone entities. An important drawback, however, is that users need to continually update the app.

Web apps are accessible via the mobile device web browser and are not downloaded onto the user's device. They can only access a limited number of the device's native features and update themselves without user intervention. This development option uses languages such as JavaScript, HTML 5, or CSS3 but no standardization or SDK is available. Web apps may also lead to higher maintenance cost across multiple mobile platforms.

From a user point of view, both options look...