Get Started. It's Free
or sign up with your email address
Cloud Concepts by Mind Map: Cloud Concepts

1. Cloud computing

1.1. On-demand self service

1.1.1. Provision computing capabilities as needed automatically without requiring human interaction with service provider

1.2. Broad network access

1.3. Resource pooling

1.4. Rapid elasticity

1.5. Measured service

2. Service Models

2.1. Tradicional IT

2.1.1. you manage

2.1.1.1. Applications

2.1.1.2. Data

2.1.1.3. Runtime

2.1.1.4. Middleware

2.1.1.5. Operating system

2.1.1.6. Virtualization

2.1.1.7. Servers

2.1.1.8. Storage

2.1.1.9. Networking

2.2. Infrastructure-as-a-service(IaaS)

2.2.1. you manage

2.2.1.1. Applications

2.2.1.2. Data

2.2.1.3. Runtime

2.2.1.4. Middleware

2.2.1.5. Operating System

2.2.2. Delivered as-a-service

2.2.2.1. Virtualization

2.2.2.2. Servers

2.2.2.3. Storage

2.2.2.4. Networking

2.3. Platform-as-a-service(Paas)

2.3.1. You Manage

2.3.1.1. Applications

2.3.1.2. Data

2.3.2. Delivered as-a-service

2.3.2.1. Runtime

2.3.2.2. Middleware

2.3.2.3. Operating System

2.3.2.4. Virtualization

2.3.2.5. Servers

2.3.2.6. Storage

2.3.2.7. Networking

2.4. Software-as-a-service (SaaS)

2.4.1. Delivered as-a-service

2.4.1.1. Applications

2.4.1.2. Data

2.4.1.3. Runtime

2.4.1.4. Middleware

2.4.1.5. Operating system

2.4.1.6. Virtualization

2.4.1.7. Servers

2.4.1.8. Storage

2.4.1.9. Networking

3. Capex v/s Opex

3.1. Capita expense Capex

3.1.1. Money Spent in Your Datacenter

3.2. Operational expense Opex

3.2.1. Eg. Your datacenter power bill

3.3. Cloud lets you trade CAPEX for OPEX

3.3.1. pay only when you consume resources

3.3.2. pay only for how much you consume

4. Cloud Terminology

4.1. High Availability(HA)

4.1.1. Full-time availability

4.1.2. Redundant hardware

4.1.3. AVOID single points-of-failure

4.1.4. Fail-over Processes

4.2. Disaster Recovery

4.2.1. Recovery Point Objective(RPO)

4.2.1.1. Transactions Lost

4.2.2. Recovery Time Objective

4.2.2.1. Down time

4.3. Fault Tolerance

4.3.1. How a cloud vendor will ensure minimal downtime for a serices

4.4. Scalability

4.4.1. Sacaling out(or in)

4.4.1.1. Horizontal scalling

4.4.2. Scalling up(or down)

4.4.2.1. Vertical scaling

4.5. Elasticity

4.5.1. Quickly increase or decrease resources

4.5.1.1. Vms

4.5.1.2. DataBase

4.5.1.3. LoadBalance

4.5.1.4. Storage

4.5.1.5. etc