3. Cloud Deployment Models
Chapter 3: Cloud Deployment Models¶
📚 What You'll Learn in This Chapter¶
By the end of this chapter, you'll understand:
- ✓ The three cloud deployment models (Public, Private, Hybrid)
- ✓ Differences between each model
- ✓ When to use each type
- ✓ Real-world scenarios for each
- ✓ Advantages and disadvantages
Time needed: 15-20 minutes
Difficulty: Beginner-friendly 🟢
Why this matters: Understanding deployment models is KEY for AZ-900 exam!
The Three Cloud Deployment Models¶
Think of it like housing options:
┌──────────────────────────────────────────────────────────────┐
│ CLOUD DEPLOYMENT MODELS = WHERE YOUR CLOUD RUNS │
│ │
│ Just like choosing where to live: │
│ │
│ 🏢 PUBLIC CLOUD = Apartment Building │
│ Share building with others, pay rent monthly │
│ │
│ 🏠 PRIVATE CLOUD = Your Own House │
│ You own it completely, but expensive │
│ │
│ 🏘️ HYBRID CLOUD = Both! │
│ Own a house + rent a vacation apartment │
│ │
└──────────────────────────────────────────────────────────────┘
Let's explore each one!
PUBLIC CLOUD¶
What Is Public Cloud?¶
Simple Definition:
You rent computing resources from a cloud provider (like Microsoft Azure). Many customers share the same physical infrastructure.
Think of it like:
An apartment building. You have your own apartment (private space), but you share the building, electricity, water, and elevators with other tenants.
How Public Cloud Works¶
┌──────────────────────────────────────────────────────────────┐
│ MICROSOFT'S DATACENTER │
│ │
│ Physical Building (Microsoft owns): │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ │ │
│ │ Server Rack 1 Server Rack 2 Server Rack 3│ │
│ │ ┌──────────────┐ ┌──────────────┐ ┌──────────┐ │ │
│ │ │Company A's │ │Company B's │ │Company C's││ │
│ │ │VMs (isolated)│ │VMs (isolated)│ │VMs ││ │
│ │ └──────────────┘ └──────────────┘ └──────────┘ │ │
│ │ │ │
│ │ Same physical servers, logically separated │ │
│ │ │ │
│ └────────────────────────────────────────────────────────┘ │
│ │
│ YOU (Company A): │
│ • Rent virtual machines │
│ • Pay monthly for what you use │
│ • Access via internet │
│ • Share hardware with others (but data is separated!) │
│ │
│ MICROSOFT: │
│ • Owns the building and servers │
│ • Maintains everything │
│ • Ensures security between customers │
│ • Handles all physical infrastructure │
│ │
└──────────────────────────────────────────────────────────────┘
Public Cloud Characteristics¶
┌──────────────────────────────────────────────────────────────┐
│ PUBLIC CLOUD KEY FEATURES │
│ │
│ 1. NO UPFRONT COSTS │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ You don't buy any hardware │ │
│ │ Start using immediately │ │
│ │ Pay monthly like a utility bill │ │
│ └──────────────────────────────────────────────────────┘ │
│ │
│ 2. INTERNET ACCESS │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Access from anywhere with internet │ │
│ │ No need to be in office │ │
│ │ Work from home, travel, anywhere! │ │
│ └──────────────────────────────────────────────────────┘ │
│ │
│ 3. SHARED INFRASTRUCTURE │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Multiple customers on same physical servers │ │
│ │ Data is logically isolated (very secure!) │ │
│ │ Cheaper because costs are shared │ │
│ └──────────────────────────────────────────────────────┘ │
│ │
│ 4. SCALABILITY │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Need more resources? Add them in minutes │ │
│ │ Need less? Remove them anytime │ │
│ │ Pay only for what you actually use │ │
│ └──────────────────────────────────────────────────────┘ │
│ │
│ 5. PROVIDER MANAGES EVERYTHING │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Hardware maintenance │ │
│ │ Physical security │ │
│ │ Power and cooling │ │
│ │ Network infrastructure │ │
│ └──────────────────────────────────────────────────────┘ │
│ │
└──────────────────────────────────────────────────────────────┘
Public Cloud Advantages¶
✅ BENEFITS:
┌──────────────────────────────────────────────────────────────┐
│ 1. LOW COST │
│ • No hardware to buy ($0 upfront) │
│ • Pay only for usage │
│ • Cancel anytime │
│ │
│ 2. NO MAINTENANCE │
│ • Provider handles all updates │
│ • No need for IT staff to manage hardware │
│ • Focus on your business, not servers │
│ │
│ 3. NEARLY UNLIMITED SCALE │
│ • Need 1 server or 1,000 servers? │
│ • Both are equally easy │
│ • Scale up/down as needed │
│ │
│ 4. HIGH RELIABILITY │
│ • Microsoft has backup power, cooling, etc. │
│ • Better than most companies can afford │
│ • 99.9%+ uptime guaranteed │
│ │
│ 5. GLOBAL REACH │
│ • Deploy to 60+ regions worldwide │
│ • Serve customers anywhere │
│ • No physical setup needed │
│ │
└──────────────────────────────────────────────────────────────┘
Public Cloud Disadvantages¶
❌ LIMITATIONS:
┌──────────────────────────────────────────────────────────────┐
│ 1. LESS CONTROL │
│ • Can't access physical servers │
│ • Limited customization options │
│ • Must follow provider's rules │
│ │
│ 2. INTERNET DEPENDENCY │
│ • Need internet to access │
│ • Slow internet = slow access │
│ • No internet = no access at all │
│ │
│ 3. DATA LOCATION │
│ • Data stored in provider's datacenter │
│ • May be in different country │
│ • Some regulations don't allow this │
│ │
│ 4. SHARED RESOURCES │
│ • Share hardware with other customers │
│ • Some industries uncomfortable with this │
│ • (Even though it's secure!) │
│ │
└──────────────────────────────────────────────────────────────┘
When to Use Public Cloud¶
✅ PERFECT FOR:
┌──────────────────────────────────────────────────────────────┐
│ • Startups (no money for servers) │
│ • Small businesses (no IT staff) │
│ • Websites and web apps │
│ • Development and testing │
│ • Apps with variable traffic │
│ • Non-sensitive data │
│ • Global applications │
│ │
│ Example: E-commerce website │
│ → Perfect! Scales during sales, cheap to start │
│ │
└──────────────────────────────────────────────────────────────┘
❌ NOT IDEAL FOR:
┌──────────────────────────────────────────────────────────────┐
│ • Highly regulated industries (sometimes) │
│ • Data that must stay in specific location │
│ • Legacy apps requiring special hardware │
│ • Ultra-high security requirements │
│ │
│ Example: Hospital patient records with strict laws │
│ → Maybe not (depends on regulations) │
│ │
└──────────────────────────────────────────────────────────────┘
PRIVATE CLOUD¶
What Is Private Cloud?¶
Simple Definition:
Computing infrastructure dedicated ONLY to your organization. You own and manage it yourself.
Think of it like:
Owning your own house. Complete control, complete privacy, but you pay for everything and maintain it yourself.
How Private Cloud Works¶
┌──────────────────────────────────────────────────────────────┐
│ YOUR COMPANY'S PRIVATE DATACENTER │
│ │
│ Your Building (You own): │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ │ │
│ │ Server Rack 1 Server Rack 2 Server Rack 3 │ │
│ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │
│ │ │ Your VMs │ │ Your VMs │ │ Your VMs │ │ │
│ │ │ Only! │ │ Only! │ │ Only! │ │ │
│ │ └──────────┘ └──────────┘ └──────────┘ │ │
│ │ │ │
│ │ ALL servers dedicated to YOUR company │ │
│ │ │ │
│ └────────────────────────────────────────────────────────┘ │
│ │
│ YOU: │
│ • Own all the hardware │
│ • Manage everything yourself │
│ • Pay upfront for equipment │
│ • Pay for electricity, cooling, staff │
│ • Complete control and privacy │
│ │
│ DIFFERENCE FROM PUBLIC: │
│ • No sharing with other companies │
│ • You handle all maintenance │
│ • Huge upfront investment │
│ • Total control over everything │
│ │
└──────────────────────────────────────────────────────────────┘
Private Cloud Characteristics¶
┌──────────────────────────────────────────────────────────────┐
│ PRIVATE CLOUD KEY FEATURES │
│ │
│ 1. DEDICATED RESOURCES │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ All servers belong to you only │ │
│ │ No sharing with other companies │ │
│ │ Maximum privacy and control │ │
│ └──────────────────────────────────────────────────────┘ │
│ │
│ 2. LOCATED ON-PREMISES │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Usually in your own building │ │
│ │ Or a datacenter you control │ │
│ │ Data stays exactly where you want it │ │
│ └──────────────────────────────────────────────────────┘ │
│ │
│ 3. YOU MANAGE EVERYTHING │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Hardware purchases and maintenance │ │
│ │ Software updates and patches │ │
│ │ Security and access control │ │
│ │ Power, cooling, physical security │ │
│ └──────────────────────────────────────────────────────┘ │
│ │
│ 4. HUGE UPFRONT COST │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ Buy servers, storage, network gear │ │
│ │ Build or rent datacenter space │ │
│ │ Hire IT staff to manage it │ │
│ │ Millions of dollars to start │ │
│ └──────────────────────────────────────────────────────┘ │
│ │
└──────────────────────────────────────────────────────────────┘
Private Cloud Advantages¶
✅ BENEFITS:
┌──────────────────────────────────────────────────────────────┐
│ 1. COMPLETE CONTROL │
│ • Configure hardware exactly how you want │
│ • Install any software │
│ • Set all security rules │
│ • No restrictions from provider │
│ │
│ 2. MAXIMUM PRIVACY │
│ • No sharing with other companies │
│ • Data never leaves your premises │
│ • You control who has physical access │
│ │
│ 3. MEET REGULATIONS │
│ • Some industries require on-premises data │
│ • Government/military often need this │
│ • Banking regulations sometimes require it │
│ │
│ 4. CUSTOMIZATION │
│ • Special hardware? Use it! │
│ • Unique security needs? Implement them! │
│ • Legacy systems? Connect them! │
│ │
│ 5. NO INTERNET DEPENDENCY │
│ • Works even if internet goes down │
│ • Fast access (local network) │
│ • No bandwidth costs │
│ │
└──────────────────────────────────────────────────────────────┘
Private Cloud Disadvantages¶
❌ LIMITATIONS:
┌──────────────────────────────────────────────────────────────┐
│ 1. EXTREMELY EXPENSIVE │
│ • $1-10 million+ to start │
│ • $500K+ yearly operating costs │
│ • Only big companies can afford │
│ │
│ 2. YOU DO ALL MAINTENANCE │
│ • Hire full IT team │
│ • Replace broken hardware │
│ • Update everything yourself │
│ • 24/7 responsibility │
│ │
│ 3. LIMITED SCALABILITY │
│ • Can only use what you bought │
│ • Need more? Buy more servers (slow!) │
│ • Stuck with what you have │
│ │
│ 4. YOUR RESPONSIBILITY IF IT BREAKS │
│ • Power outage? You fix it │
│ • Cooling fails? You handle it │
│ • Server dies? You replace it │
│ │
│ 5. NO GLOBAL REACH │
│ • Limited to your locations │
│ • Expensive to expand internationally │
│ • Can't easily serve global customers │
│ │
└──────────────────────────────────────────────────────────────┘
When to Use Private Cloud¶
✅ PERFECT FOR:
┌──────────────────────────────────────────────────────────────┐
│ • Banks (strict regulations) │
│ • Government agencies (security requirements) │
│ • Healthcare (patient privacy laws) │
│ • Large enterprises (have money and staff) │
│ • Data that MUST stay on-premises by law │
│ • Legacy systems with special hardware needs │
│ │
│ Example: National defense system │
│ → MUST use private cloud (security!) │
│ │
└──────────────────────────────────────────────────────────────┘
❌ NOT IDEAL FOR:
┌──────────────────────────────────────────────────────────────┐
│ • Startups (too expensive) │
│ • Small businesses (can't afford it) │
│ • Projects needing quick scaling │
│ • Companies without IT expertise │
│ • Global applications │
│ │
│ Example: New mobile app startup │
│ → Terrible idea! Use public cloud instead │
│ │
└──────────────────────────────────────────────────────────────┘
HYBRID CLOUD¶
What Is Hybrid Cloud?¶
Simple Definition:
Combination of public and private cloud. Use both, connected together.
Think of it like:
Owning a house + renting a vacation apartment when needed. Best of both worlds!
How Hybrid Cloud Works¶
┌──────────────────────────────────────────────────────────────┐
│ HYBRID CLOUD ARCHITECTURE │
│ │
│ YOUR PRIVATE CLOUD AZURE PUBLIC CLOUD │
│ ┌─────────────────────┐ ┌──────────────────┐ │
│ │ Your Datacenter │◄─Connection─►│ Microsoft's │ │
│ │ │ (Secure) │ Datacenter │ │
│ │ • Sensitive data │ │ │ │
│ │ • Legacy systems │ │ • Public website │ │
│ │ • Core databases │ │ • Test systems │ │
│ │ │ │ • Burst capacity │ │
│ └─────────────────────┘ └──────────────────┘ │
│ │
│ CONNECTED & WORKING TOGETHER! │
│ │
│ Example Flow: │
│ 1. Customer visits your website (Azure public cloud) │
│ 2. Website needs customer data (private cloud) │
│ 3. Data flows securely between clouds │
│ 4. Customer sees their info! │
│ │
└──────────────────────────────────────────────────────────────┘
Hybrid Cloud Scenarios¶
Scenario 1: Banking Application
┌──────────────────────────────────────────────────────────────┐
│ BANK USING HYBRID CLOUD │
│ │
│ PRIVATE CLOUD (On-Premises): │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ What stays private: │ │
│ │ • Customer account data (regulations require it!) │ │
│ │ • Transaction processing │ │
│ │ • Core banking systems │ │
│ │ │ │
│ │ Why: Legal requirements, maximum security │ │
│ └────────────────────────────────────────────────────────┘ │
│ ↕ Secure Connection │
│ PUBLIC CLOUD (Azure): │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ What goes public: │ │
│ │ • Mobile banking app │ │
│ │ • Public website │ │
│ │ • Customer service chatbot │ │
│ │ • Marketing campaigns │ │
│ │ │ │
│ │ Why: Scales easily, cheaper, global reach │ │
│ └────────────────────────────────────────────────────────┘ │
│ │
│ BENEFITS: │
│ • Meets legal requirements (private data stays on-premises) │
│ • Saves money (public cloud cheaper for websites) │
│ • Scales well (can handle traffic spikes) │
│ • Best of both worlds! │
│ │
└──────────────────────────────────────────────────────────────┘
Scenario 2: Manufacturing Company
┌──────────────────────────────────────────────────────────────┐
│ MANUFACTURER USING HYBRID CLOUD │
│ │
│ PRIVATE CLOUD (Factory): │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ • Factory floor control systems │ │
│ │ • Machine monitoring │ │
│ │ • Production planning │ │
│ │ • Inventory management │ │
│ │ │ │
│ │ Why: Real-time control, no internet dependency │ │
│ └────────────────────────────────────────────────────────┘ │
│ ↕ │
│ PUBLIC CLOUD (Azure): │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ • E-commerce website │ │
│ │ • Customer orders │ │
│ │ • Data analytics │ │
│ │ • AI/ML for predictions │ │
│ │ │ │
│ │ Why: Customer-facing, needs to scale │ │
│ └────────────────────────────────────────────────────────┘ │
│ │
│ FLOW: │
│ Customer orders online (Azure) → Order sent to factory │
│ (private) → Factory produces → Ships → Website updates │
│ (Azure) │
│ │
└──────────────────────────────────────────────────────────────┘
Hybrid Cloud Advantages¶
✅ BENEFITS:
┌──────────────────────────────────────────────────────────────┐
│ 1. FLEXIBILITY │
│ • Choose best location for each workload │
│ • Keep sensitive data private │
│ • Put public data in cloud │
│ │
│ 2. COST OPTIMIZATION │
│ • Keep existing on-premises investment │
│ • Add cloud only where it makes sense │
│ • Don't waste money replacing working systems │
│ │
│ 3. MEET REGULATIONS │
│ • Keep regulated data on-premises │
│ • Everything else in cheaper cloud │
│ • Comply with laws while saving money │
│ │
│ 4. SCALABILITY WHEN NEEDED │
│ • Normal traffic: Use private cloud │
│ • Traffic spike: Burst to public cloud │
│ • Pay for extra capacity only when used │
│ │
│ 5. GRADUAL MIGRATION │
│ • Move to cloud slowly over time │
│ • No "big bang" migration │
│ • Reduce risk │
│ │
└──────────────────────────────────────────────────────────────┘
Hybrid Cloud Disadvantages¶
❌ LIMITATIONS:
┌──────────────────────────────────────────────────────────────┐
│ 1. COMPLEX TO MANAGE │
│ • Two environments to manage │
│ • Need expertise in both │
│ • More moving parts │
│ │
│ 2. INTEGRATION CHALLENGES │
│ • Must connect private and public clouds securely │
│ • Data needs to move between them │
│ • Authentication across both │
│ │
│ 3. COSTS BOTH PLACES │
│ • Still paying for private infrastructure │
│ • Also paying for public cloud │
│ • Potentially expensive if not optimized │
│ │
│ 4. REQUIRES PLANNING │
│ • Need to decide what goes where │
│ • Design how they connect │
│ • Plan for data movement │
│ │
└──────────────────────────────────────────────────────────────┘
When to Use Hybrid Cloud¶
✅ PERFECT FOR:
┌──────────────────────────────────────────────────────────────┐
│ • Large enterprises with existing datacenters │
│ • Regulated industries (finance, healthcare, government) │
│ • Companies transitioning to cloud │
│ • Businesses with variable workloads │
│ • Organizations with data sovereignty requirements │
│ │
│ Example: Hospital system │
│ → Patient records private (regulations) │
│ → Appointment scheduling public (convenience) │
│ → Perfect hybrid use case! │
│ │
└──────────────────────────────────────────────────────────────┘
Comparison Summary¶
┌──────────────────────────────────────────────────────────────────────────┐
│ QUICK COMPARISON │
├──────────────────────────────────────────────────────────────────────────┤
│ │
│ Feature PUBLIC PRIVATE HYBRID │
│ │
│ Cost 💰 Low 💰💰💰 High 💰💰 Medium │
│ Control ⭐⭐ Low ⭐⭐⭐⭐⭐ Max ⭐⭐⭐ Medium │
│ Scalability ⭐⭐⭐⭐⭐ ⭐ Low ⭐⭐⭐⭐ High │
│ Maintenance ✅ Provider ❌ You ⚠️ Both │
│ Internet ✅ Required ❌ Not needed ⚠️ For public part │
│ Deployment ⚡ Minutes 🐌 Months ⚡🐌 Varies │
│ Best For Startups Big corps Enterprises │
│ │
└──────────────────────────────────────────────────────────────────────────┘
Real-World Decision Tree¶
┌──────────────────────────────────────────────────────────────┐
│ WHICH MODEL SHOULD YOU USE? │
│ │
│ START: What type of organization are you? │
│ │
│ Small business/startup? │
│ └─YES→ PUBLIC CLOUD (Azure) ✓ │
│ │ │
│ NO │
│ ↓ │
│ Do you have legal requirements for data location? │
│ └─YES→ Do you have millions to spend? │
│ └─YES→ PRIVATE CLOUD ✓ │
│ └─NO→ HYBRID CLOUD ✓ │
│ │ │
│ NO │
│ ↓ │
│ Do you have existing on-premises infrastructure? │
│ └─YES→ HYBRID CLOUD (gradual migration) ✓ │
│ │ │
│ NO │
│ ↓ │
│ PUBLIC CLOUD (most flexible & cheapest) ✓ │
│ │
└──────────────────────────────────────────────────────────────┘
📝 Chapter Summary¶
Key Points to Remember:
✅ Three Deployment Models
Public Cloud: - Shared infrastructure - Cheapest option - Provider manages everything - Azure, AWS, Google Cloud
Private Cloud: - Dedicated to your organization - Most expensive - You manage everything - Maximum control
Hybrid Cloud: - Combination of both - Best flexibility - More complex - Good for transition
✅ When to Use Each - Public: Most common, default choice - Private: Strict regulations, huge budgets - Hybrid: Large enterprises, gradual migration
✅ Key Differences - Cost: Public < Hybrid < Private - Control: Private > Hybrid > Public - Complexity: Private > Hybrid > Public
✅ Self-Check¶
□ Can you explain the three models using the housing analogy?
□ Know when to use each deployment model?
□ Understand shared vs. dedicated infrastructure?
□ Can you give a real example of hybrid cloud?
🎯 Practice Questions¶
Question 1: Which deployment model shares physical infrastructure among multiple customers?
A) Private Cloud
B) Hybrid Cloud
C) Public Cloud
D) None of the above
Question 2: A bank must keep customer data on-premises due to regulations, but wants to use cloud for their public website. Which model?
A) Public Cloud
B) Private Cloud
C) Hybrid Cloud
D) Community Cloud
Question 3: Which is TRUE about public cloud?
A) You own all the servers
B) Only one customer uses the datacenter
C) Infrastructure is shared among customers
D) Requires no internet access
Question 4: What's the main disadvantage of private cloud?
A) Low security
B) Very expensive
C) Cannot scale
D) No control
Question 5: A startup with no IT staff wants to launch a mobile app. Best choice?
A) Private Cloud - maximum control
B) Public Cloud - easy and cheap
C) Hybrid Cloud - best of both
D) Build own datacenter
✍️ Practice Answers¶
Question 1: C - Public Cloud
Explanation: Public cloud is characterized by shared infrastructure where multiple customers' workloads run on the same physical servers (though logically isolated).
Question 2: C - Hybrid Cloud
Explanation: Perfect hybrid scenario! Sensitive data stays on-premises (private), public website in cloud (public), connected together.
Question 3: C - Infrastructure is shared among customers
Explanation: In public cloud, customers share physical infrastructure. Data is logically separated and secure, but hardware is shared to reduce costs.
Question 4: B - Very expensive
Explanation: Private cloud's main disadvantage is extreme cost - millions upfront for hardware, plus ongoing operational costs. Only large organizations can afford it.
Question 5: B - Public Cloud - easy and cheap
Explanation: Startup with no IT staff should absolutely use public cloud. It's cheap to start, no maintenance required, and scales easily. Private cloud would be impossible for them to afford.
🔖 Quick Reference Card¶
┌──────────────────────────────────────────────────────────────┐
│ CLOUD DEPLOYMENT MODELS CHEAT SHEET │
├──────────────────────────────────────────────────────────────┤
│ │
│ PUBLIC CLOUD (Azure, AWS, Google Cloud) │
│ • Shared infrastructure │
│ • Low cost, no upfront payment │
│ • Internet access required │
│ • Provider manages everything │
│ • Best for: Startups, small businesses, most apps │
│ │
│ PRIVATE CLOUD (Your own datacenter) │
│ • Dedicated infrastructure │
│ • Very expensive ($millions) │
│ • You manage everything │
│ • Maximum control and privacy │
│ • Best for: Banks, government, strict regulations │
│ │
│ HYBRID CLOUD (Both connected) │
│ • Mix of public and private │
│ • Medium cost and complexity │
│ • Flexible - best of both worlds │
│ • Requires careful planning │
│ • Best for: Large enterprises, regulated industries │
│ │
│ DEFAULT CHOICE: Public Cloud (90% of scenarios) │
│ │
└──────────────────────────────────────────────────────────────┘
End of Chapter 3 ✓
Ready for Chapter 4: Hybrid Technologies! 🚀 -e