Please enable JavaScript.
Coggle requires JavaScript to display documents.
Cloud Deployment Models - Coggle Diagram
Cloud Deployment Models
-
Public, Private, Community and Hybrid.
-
-
Which criteria are used to evaluate the choose of the model. (Elasticity, control level, cost, security,…)
-
-
COMMUNITY CLOUD
- Definition and explanation
Infrastructure shared by several organizations with common concerns (mission, security, compliance, policy)
Owned and managed by one or more members, by a third party, or a combination
-
-
Advantages: shared costs, compliance adapted to a sector, collaboration
Limits: shared capacity, governance complexity, less flexible
Organizations in the same sector with identical rules: government, healthcare, education, finance
-
Collaborative projects (research consortiums, joint ventures)
-
-
-
-
Cost: MEDIUM (split among members, cheaper than private)
-
-
-
AWS GovCloud (US): isolated cloud region for US government agencies and regulated industries with specific compliance needs
-
-
HYBRID CLOUD
- Definition and explanation
-
-
-
-
Advantages: flexibility, cost optimization, gradual migration
Limits: integration complexity, harder security and management
-
-
Control level: FLEXIBLE (high on private part, lower on public part)
-
-
Interoperability: key criterion (APIs, networking, portability)
-
-
-
PUBLIC CLOUD
- Definition and explanation
Cloud services owned and operated by a third-party provider (AWS, Microsoft Azure, Google Cloud)
Resources (servers, storage, network) are shared between many customers (multi-tenant)
Accessed over the Internet, self-service, pay-as-you-go
The provider manages hardware, maintenance and updates
Advantages: no upfront investment, fast deployment, global reach
Limits: less control, data location concerns, vendor lock-in
-
Workloads with unpredictable or seasonal peaks (e-commerce, streaming, events)
Development, testing and prototyping environments
Web applications, SaaS products, big data and AI workloads
-
-
Elasticity: VERY HIGH (scale up/down in minutes, near-unlimited capacity)
-
Cost: LOW entry cost, OPEX model, pay only for usage (can grow with heavy use)
Security: shared responsibility model, strong provider security but less customization
Compliance: depends on provider certifications (ISO 27001, SOC 2, GDPR)
Performance: good, variable under shared load
-
Netflix: after a major database failure in 2008, it moved from its own data centers to AWS (migration completed in 2016) to stream worldwide and absorb huge audience peaks
Airbnb: built on AWS from the start, scaling quickly with booking peaks without owning data centers
Spotify: migrated its infrastructure to Google Cloud to benefit from data processing and analytics services
PRIVATE CLOUD
- Definition and explanation
-
Hosted on-premise (own data center) or by a hosting provider, managed internally or by a third party
Built with virtualization and cloud software (VMware, OpenStack, Kubernetes)
Offers cloud benefits (self-service, automation) with dedicated resources
Advantages: full control, high security, customization
Limits: high cost, maintenance effort, limited scalability
Highly sensitive data: banking, healthcare, defense, government
Strict regulations and data sovereignty requirements (GDPR, local laws)
-
-
-
-
-
Control level: TOTAL (hardware, network, security policies)
Cost: HIGH (CAPEX for hardware, staff, maintenance, energy)
Security: VERY HIGH (isolated, dedicated environment)
-
-
-
-
eBay: runs a large OpenStack-based private cloud for its marketplace platform, keeping control over performance and data
Bank of America: built an internal private cloud to keep sensitive financial data under its control and reportedly reduced infrastructure costs