Module 1 - Cloud Concepts

Cloud Models

Cloud Services

Private - (CapEx)

Hybrid

Public - (OpEx)

Paas

SaaS

Iaas - requires the most user-management

Important Concepts

Capital Expenditure (CapEx) - This is the spending of money on physical infrastructure up front, and then deducing that expense from your tax bill over time.

Operational Expenditure (OpEx) - This is spending money on services or products now and being billed for them now. Companies get into market quickly and pay as much or as little for the infrastructure as the business requires

Economies of Scale

Elasticity - the ability to automatically/dynamically increase/decrease resources as needed

Scalability - the abillity to increase or decrease resources for any given workload

Agility - the ability to react quickly. Cloud services can allocate and deallocate resources quickly. On-demand via self-service

High Availability - the ability to keep services up and running for long periods of time, with very little downtime

Fault Tolerance - The ability to remain up and running even in in the event of a component or service no longer functioning. If one component fails, a backup component takes its place

Disaster Recovery - the ability to recover from an event which has taken down a cloud service . Can happen very quickly with automation and services being readily available to use.

Consumption-based Model - end users only pay for the resources that they use

Characteristics

Scaling-out - adding additional resources to service a workload

Scaling-up - adding additional capabilities to manage an increase in demand to the existing resources

Ex: storage costs have decreased significantly over the last decade due to CSP's ability to purchase large amounts of storage at significant discounts

the ability to reduce costs and gain efficiency when operating at a larger scale, in comparison to operating at smaller scales

no need to purchase and manage costly infrastructure that they may or may not use to its fullest

the ability to pay for for additional resources when they are needed

no upfront costs

the ability to stop paying for resources that are no longer needed

Characteristics

Ownership - resources do not belong to org using them, they are owned and operated by the cloud services provider

Skills - do not require deep tech knowledge

Multiple End-users - PC modes may make their resources available to multiple orgs

Public Access - provides access to the public

Availability - this is the most common deployment model

Connectivity - users and orgs are typically connected to the PC over the internet using a web browser

Public Acccess - does not provide access to the public

Users - PC operates only within one org and cloud computing resources are used exclusively by a single business/org

Ownership - the owner and the user of the cloud services are the same

Connectivity - made over a private network that is highly secure

Skills - requires deep technical knowledge

Hardware - the owner is entirely responsible for the purchase, maintenance, and management of the cloud HW

Control - orgs retain management control in private clouds

Resource Location - specific resources run or are used in a public cloud and others run or are used in a private cloud

Skills - tech skills are required to maintain the private cloud and ensure both models can operate together

Cost Efficiency - allows an org to leverage some of the benefits of cost, efficiency and scale that are available with a public model

Characteristics

Upfront Cost - no upfront costs, pay for what you consume

User Ownership - user is responsible for purchase, installation, config and management of their own software Os, middleware and application

CSP Ownership - responsible for ensuring that underlying cloud infrastructure is available for the user

Upfront Cost - no upfront costs, pay for what you consume

User Ownership - users are responsible for the development of their own apps, but they are not responsible for managing the server or infrastructure

CSP Ownership - typically responsible for everything apart from the application that a user wants to run

Upfront Costs - no upfront costs, pay as a subscription

User Ownership - users just use the application software

CSP Ownership - is responsible for the provisioning, management, and maintenance of the application software

Use Case: Development Framework

provides a framework that developers can build upon to develop or customize applications

features such as high-availability, scalability and multi-tenant capability are included (reduces coding for developers)

Use Case: Migrating Workloads

managed in a similar way as on premises infrastructure and provide an easy migration path for moving existing apps to the cloud

Use Case: Office 365, Skype & Microsoft Dynamics CRM