Scribd
Upload
53 views

Cloud Computing Mindmap

Uploaded by

y2cs8hp5w7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
53 views

Cloud Computing Mindmap

Uploaded by

y2cs8hp5w7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Cloud Computing

Layer 1: Cloud vs. On-Premise


On-Premise Computing

Definition: Hosting IT resources within the organization’s own


infrastructure.
Features: Full control, high CapEx, maintenance responsibility.
Components: Server clusters, data centers, physical security.
Challenges: High initial cost, scaling complexity.

Cloud Computing

Definition: Delivery of computing resources and services over the


internet by third-party providers.
Features: Scalability, cost savings, flexibility.
Early Models: Grid computing, utility computing.
Advantages: Rapid scalability, centralized security, reduced CapEx.
Limitations: Internet dependency, vendor lock-in, security concerns.

Key Differences

Ownership: Organization (On-Premise) vs. Provider (Cloud).


Cost: High CapEx (On-Premise) vs. Pay-as-you-go OpEx (Cloud).
Maintenance: Manual updates (On-Premise) vs. Managed by provider
(Cloud).
Scalability: Fixed resources (On-Premise) vs. Elastic resources (Cloud).

Layer 2: Cloud Components


Cloud Architecture

Front-End

Devices: Laptops, smartphones, user applications.


Client-side interaction with cloud services.

Back-End

Data centers, servers, storage systems managed by cloud providers.

Middleware

Connects front-end and back-end.


APIs, management interfaces, workflow orchestration.

Network

Ensures data transmission between front-end, middleware, and back-


end.
Virtual Private Networks (VPN), internet, Content Delivery
Networks (CDN).

Virtualization

Key to cloud services.


Types: Server, storage, and network virtualization.
Hypervisors: Type 1 (Bare-metal) and Type 2 (Hosted).

Security and Governance

Centralized security provided by cloud providers.


Identity and Access Management (IAM), encryption, compliance.

Layer 3: Cloud Deployment Models


Public Cloud

Definition: Cloud services delivered over the internet by third-party


providers.
Features: Scalability, cost-effectiveness, no infrastructure management.
Use Cases: Startups, high-growth tech, seasonal applications.

Private Cloud

Definition: Dedicated cloud infrastructure for one organization.


Features: Full control, high security, customization.
Challenges: High cost, limited scalability.
Use Cases: Regulated industries like finance, healthcare.

Hybrid Cloud

Definition: Combines public and private clouds for flexibility and


control.
Features: Data mobility, disaster recovery, cost control.
Use Cases: Businesses with complex data needs and regulatory concerns.

Community Cloud

Definition: Shared cloud infrastructure among organizations with similar


needs.
Features: Cost-sharing, collaboration, tailored services.
Use Cases: Government agencies, research organizations.

Layer 4: Cloud Service Models


Infrastructure as a Service (IaaS)

Provides cloud-hosted infrastructure (virtual machines, storage,


networks).
Features: High availability, scalability, disaster recovery.
Use Cases: Disaster recovery, eCommerce, IoT.

Platform as a Service (PaaS)

Provides platforms for developers to build, deploy, and manage


applications.
Features: Middleware services, automatic updates, support for multiple
languages.
Use Cases: Agile development, DevOps, IoT.

Software as a Service (SaaS)


Software applications delivered over the internet.
Features: Multi-tenancy, accessibility from any device, minimal setup.
Use Cases: Productivity tools, CRM systems, email services.

Layer 5: Performance Monitoring and Management


CPU Utilization

Monitors how much of the CPU’s capacity is being used.


Important for autoscaling decisions.

Mean Time to Repair (MTTR)

Measures how quickly a system can be restored after a failure.

Requests Per Minute (RPM)

Tracks the number of requests a server handles in a minute.


Helps understand traffic spikes and server load.

Error Rate

Monitors the percentage of failed requests.


Indicates system issues like configuration errors or overloading.

You might also like