Cloud Computing

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

1. Economics of cloud computing

1.1. Fixed application labour amortized over a large number of customers

1.1.1. Meaningful reduction in overall cost for complex application in the long run

1.2. Larger pool of resources, smoother aggregate demand profile, higher overall utilization rate.

1.2.1. Cheaper

1.3. Reduce time-of-day variability

1.3.1. Synchronized workplace

1.4. Pay-as-you-go pricing, self-service

1.4.1. Saves cost

1.5. Multi-resource diversification

1.5.1. Optimize workload

1.6. Higher expectation of performance

1.6.1. No resource constraints

1.7. Cost of Power

1.7.1. Large provider can pay for inexpensive electricity due to bulk purchase agreement. Low energy cost.

2. Cloud Risks

2.1. People Risks

2.1.1. Multi-tenancy Risks

2.1.1.1. Perfomance

2.1.1.1.1. Several users utilizing the same cloud hardware/storage

2.1.1.2. Vulnerability to hackers

2.1.1.2.1. Risk of data being attacked

2.1.2. User Management Risks

2.1.2.1. Identity management and authentication

2.1.2.1.1. Risk of unauthorized usage/access, or authorized users not being able to access

2.1.2.2. Data Access

2.1.2.2.1. Some data should be encrypted or unaccessible

2.1.2.3. User Permissions

2.1.2.3.1. Risk of users having unwarranted administrative privileges

2.1.2.4. Physical access to servers

2.1.2.4.1. Unauthorized users having access to data center

2.2. Financial and Legal Risks

2.2.1. Fiancial Risks

2.2.1.1. Return on Investment (ROI)

2.2.1.1.1. Cloud momentum may stop

2.2.1.1.2. Protect: perform a financial analysis prior migration

2.2.1.2. Not Scaling back resourses

2.2.1.2.1. Not scaling back resourses when done

2.2.1.2.2. Protect: Implement financial monitoring, usage and maximums for all purchases

2.2.1.3. Over provisioning of resourses

2.2.1.3.1. acquiring too much capacity

2.2.1.3.2. Prevent: conduct needs analysis with Subject Matter Experts (SMEs)

2.2.1.4. Under provisioning of resourses

2.2.1.4.1. not enough resources are available or too constrained

2.2.1.4.2. Protect: Monitor usage and get feedbacks from users

2.2.2. Legal Risks

2.2.2.1. Location

2.2.2.1.1. regional events

2.2.2.1.2. Jurisdiction

2.2.2.2. Failure to pay

2.2.2.2.1. what happened to the data when you stop paying? delete, held on for 1 week, month ?

2.2.2.2.2. Protection: Clearly define data retention due to non-payment in the SLA

2.2.2.3. Licensing

2.2.2.3.1. Licensing is not monitored agreements are violated

2.2.2.3.2. Protection: Educate VM creators on licensing agreements and restrictions

2.2.2.4. Seizure

2.2.2.4.1. Law enforcement can seize server

2.2.2.4.2. Mitigate: Replicate data or private cloud

2.3. Availability Risks

2.3.1. Outages

2.3.1.1. ISP

2.3.1.1.1. Risk of internet outage which results in no access to cloud resources

2.3.1.2. Termination of Service

2.3.1.2.1. Risk of primary cloud vendor going down

2.3.2. Backup and Disaster Recovery

2.3.2.1. Business Continuity

2.3.2.1.1. Risk of a disastrous halt of service/production

2.3.2.1.2. Risk of having an undefined backup management

2.3.2.2. Disaster Recovery

2.3.2.2.1. Risk of data lost during site disaster

2.3.2.2.2. Risk of not being able to access replicated data

3. ROI Considerations

3.1. IaaS

3.1.1. Storage and Computation costs

3.1.2. Bandwidth requirements

3.1.2.1. It is online, need bandwidth to download and upload

3.1.3. Service Level agreements

3.1.3.1. Promised uptime. More uptime = more money

3.1.4. Cloud benefits

3.1.4.1. Scalability

3.1.4.2. Expandability

3.1.4.3. Flexibility

3.1.4.3.1. Speed of deployment

3.1.5. Security and governance

3.1.5.1. More costly as it is more complex for cloud

3.1.6. Support

3.1.6.1. IT support

3.2. PaaS

3.2.1. Application Development

3.2.1.1. Cost of hardware/software

3.2.1.2. Possible 30% - 40% savings

3.2.2. Application Testing

3.2.2.1. Avoid cost associated with keeping extra hardware just for testing purposes

3.2.2.2. Possible 70% - 90% saving, if we can find a suitable service provider

3.2.3. Application Deployment & Mangement

3.2.3.1. Auto Provisioning Auto Scaling

3.2.3.1.1. Instantly added those needed to support application processing, database processing and storage

3.2.3.2. Saving come form being free from the work to upgrading data centers, 50% - 60% reduction costs

3.3. SaaS

3.3.1. App in-house vs on-demand

3.3.2. Evaluation model for software

3.3.2.1. Different modes of subscriptions

3.4. Other Consideration

3.4.1. CAPEX vs OPEX

3.4.2. Migration Issues

3.4.2.1. Security

3.4.2.1.1. Checking the cloud provider's audit and certification.

3.4.2.2. Vendor Management

3.4.2.2.1. Requires the need to manage SLA and customers have to monitor the services.

3.4.2.3. Technical Integration

3.4.2.3.1. Services offered/built into the cloud.