Cloud Services Provide
- Availability
- Scalability / Dynamic adjust for current workload (up or out)
- Elasticity / Providing scalability automatically
- Agility / React quickly
- Disaster Recovery
- Fault Tolerance
- Latency
- Global Reach
- Security
- Predictive Cost
Things to consider for cost when using Cloud
- Economies of Scale – Cloud providers have far larger resources therefore able to provide for cheaper
- Capital Expenditure (CapEx) – spending money up front on physical infrastructure, then deducting that expense over time. Value decreases over time.
- Operational Expenditure (OpEx) – spending money for services used right now. No upfront cost, it is a pay as used service. Deductions are for current year only, no value decrease over time.
- Consumption Based Model – Cloud is OpEx, you only pay for what is used. Ability to pay more as more needed, or pay less if needs drop.
Types of Cloud Models
- Public Cloud – owned by host, connection over secure network and typically over internet.
- Ownership – resources are owned by host. Pay for usage
- Multiple End Users – makes resources available to multiple end users
- Public Access
- Skills – since public resources the skill set is common
- No CapEx, yes OpEx
- Consumption-based Model
- Some concerns with Public Cloud:
- Security
- Compliance
- Ownership – user organization dont own resources so cannot control
- Specific Scenarios – ex support lagacy equipment that cloud vendor does not have
- Private Cloud – owned and operated by user organization. Resides in their own datacenter and managed by user organization. Used when data must reside physically in location – example Medical or Government.
- Ownership – resources owned by user. Pay for usage
- Control – totally done by user
- Connectivity – private
- Public Access – none
- Some concerns with Private Cloud:
- Upfront CapEx
- Lack of agility
- Higher maintenance
- Skills required is more specific, harder to find
- Hybrid Cloud – mix of public and private cloud
Types of Cloud Services
- IaaS (Infrastructure as a Service)
- Virtual Machines, storage, networks, OS, whole infrastructure
- No upfront costs
- User ownership – user required to maintain the infrastructure
- Cloud ownership – physical layer and its availability to user
- Shared Responsibility – both user and cloud provider responsible for infrastructure
- PaaS (Platform as a Service)
- Host manages infrastructure
- Fast deployment, user only focus on platform
- No upfront costs
- User ownership – user responsible for apps running on the platforms
- Cloud ownership – cloud provider manages the underlying infrastructure and physical layer
- Limitations of the platform – depending on what service the host is providing, may not fit to all types of workloads
- SaaS (Software as a Service)
- Provider hosts and manages whole software system
- No upfront costs – usually a subscription model
- User Ownership – minimal
- Cloud Ownership – responsible for provisioning, management and maintenance
- Office 365, Micrsoft Skype, etc.
- Limitations of the software
References
‘