Cloud Components

Cloud Components & Deployment Models
Lesson 2 · Deployment

Cloud Components & Deployment Models

Every cloud service is really just three parts working together — and how those parts get shared, split, or isolated is what defines a deployment model. Explore each piece below.

2.6

Cloud Components

Every cloud services solution comes down to three parts: the client platform accessing the service, the data center hosting it, and the network connecting the two. Tap each to see its role.

Client
Network
CSP Data Center
Client — the means of access for a cloud services consumer: phones, tablets, computers, IoT devices, or servers, running Windows, macOS, Linux, iOS, or Android.
2.7 – 2.11

Deployment Models

The same cloud infrastructure can be managed internally, offered by a provider to many organizations, or some mix of both. Step through each model below.

Hybrid

Combines an organization's on-premises and cloud environments — typically supported by a single cloud service provider.

Multi-cloud

Uses cloud services from multiple cloud service providers — e.g. apps in Azure, databases in AWS.

2.12

Virtual Private Cloud

A VPC hosts your organization's services inside a public CSP's infrastructure — but in an isolated segment, unshared with other tenants. It's easy to confuse with a private cloud. The difference is what kind of isolation you get.

CSP SHARED INFRASTRUCTURE
Your isolated segment
SCALABILITYHigh
VPC — logical isolation of the cloud deployment, still running on the CSP's shared infrastructure. Because it rides on the CSP's full capacity, it scales easily.
2.13

Multitenancy

Multitenancy is the concept behind public cloud: multiple tenants share computing resources owned by the CSP — the opposite idea of a VPC. It's what makes shared resources cost-effective, but it also means one tenant's spike can affect another's performance.

Tenant ATenant BTenant CTenant DTenant E
All tenants drawing steady, predictable resource shares.
CSPs address this with service level agreements (SLAs) — worth reviewing closely against your security, availability, scalability, and performance requirements before you sign on.
§ 2.6–2.13 · Cloud Components & Deployment Models