2. âą Simply stated: Cloud = Internet
âą So..Cloud Computing = Internet based computing
âą More precisely, Cloud computing is:
â« using information technology as a service.
â« having services that are available over a network.
â« using encapsulated services that have anAPI.
â« adding to the efficiency for deploying applications.
â« billing by consumption
4. ï§ Cloud Software as a Service (SaaS)
ïș Use providerâs applications over a network
ïș Example: Facebook, SalesForce.com, Gmail
ï§ Cloud Platform as a Service (PaaS)
ïș Deploy customer-created applications to a cloud
ïș Give me nice API and take care of the implementation
ïș Example: Google App Engine , Microsoft Azure
ï§ Cloud Infrastructure as a Service (IaaS)
ïș Rent processing, storage, network capacity, and other
fundamental computing resources
ïș 3Tier, Amazon EC2, Rackspace, GoGRID
5. ï§ Cloud computing often leverages:
ï Massive scale
ï Homogeneity
ï Virtualization
ï Resilient computing
ï Low cost software
ï Geographic distribution
ï Service orientation
ï Advanced security technologies
6. 4 Cloud Deployment Models
ï§ Private cloud
ïș enterprise owned or leased
ï§ Community cloud
ïș shared infrastructure for specific community
ï§ Public cloud
ïș Sold to the public, mega-scale infrastructure
ï§ Hybrid cloud
ïș composition of two or more clouds
7. Based upon original chart created by Alex Dowbor - http://ornot.wordpress.com
Deployment
Models
Service
Models
Essential
Characteristics
Common
Characteristics
Software as a Service
(SaaS)
Platform as a Service
(PaaS)
Infrastructure as a
Service (IaaS)
Resource Pooling
Broad Network Access Rapid Elasticity
Measured Service
On Demand Self-Service
Low Cost Software
Virtualization ServiceOrientation
Advanced Security
9. Amazon Web Services
ï§ Elastic Compute Cloud (EC2)
ïș Rent computing resources by the hour
ïș Basic unit of accounting = instance-hour
ïș Additional costs for bandwidth
ï§ Simple Storage Service (S3)
ïș Persistent storage
ïș Charge by the GB/month
ïș Additional costs for bandwidth
17. CSAL Namespaces
One namespace for each abstraction type
ï§ Metadata only for containers
ï§Service endpoint, identifier, user credentials
ï§Each abstraction has an independent
metadata store
âą Metadata cachingContainer ops are not very
common
âą If data is stale, simply re-fetch and retry