Module 0 - Core Cloud Concepts Flashcards
Understanding of core concepts in Cloud Computing, cost factors and considerations.
What are the three (3) types of Cloud Computing Service categorizations and what is the main difference between them?
IaaS, PaaS, SaaS
Main differences between the three are how much YOU manage vs how much the Cloud Vendor manages
IaaS, who manages what, and Azure-specific examples
Infrastructure as a Service
Examples:
• Azure
• AWS
• Google Compute Engine
What gets managed by who?
• The Cloud Vendor manages Virtualization, Servers, Storage, Networking
• You manage Apps, Data, Runtime, Middleware, OS
Azure-specific:
• Azure Compute, Virtual Machines, Azure Storage
PaaS, who manages what, and Azure-specific examples
Platform as a Service
Examples:
• Azure Logic Apps
• Heroku
• Amazon Elastic Beanstalk
What gets managed by who?
• The Cloud Vendor manages Virtualization, Servers, Storage, Networking, Runtime, Middleware, OS
• You manage your Application and your Data 😉
Azure-specific:
Azure Logic Apps, Azure Functions, Azure Web Jobs, Azure Automation
SaaS, who manages what, and Azure-specific examples
Software as a Service
Examples:
• Office 365
• DropBox
• SalesForce
• Dayforce!
What gets managed by who?
• The Cloud Vendor manages EVERYTHING (Kareo, Salesforce). Usually a full web application
Azure-specific:
Word, SharePoint, OneDrive, Teams, etc.
On-Prem, who manages what?
You manage everything! it’s “on-premises”
Hint: D&T S S&B HPC BDA
IaaS - What are some Service Scenarios?
- Development & Testing
- Scaling - Turn on/off dev machines when needed, no need to pay for having full-time hardware
- Storage and Backups - relatively cheap to maintain backups
- High Performance Computing on tap
- Big Data Analysis - you only pay for the time you need
PaaS - What are some Service Scenarios?
Analytics/BI: tools provided as a service allow companies to analyze and mine their data (Power BI for example, IoT Dashboard, Azure Monitor, etc. etc.)
Development: You can create apps using cloud services, gaining much scalability, availability and reliability within your application (i.e. every service in Azure Compute)
Describe the “Public Cloud”…what is it?
A vendor that provides Cloud Services. Usually shared among multiple clients through secured access, supported by shared backend hardware
Azure is a Public Cloud, so is Google Apps
SaaS - What are some Service Scenarios?
- Getting access to sophisticated apps WITHOUT having to manage infrastructure or scaling
- Instant access to features for managing your data, on both Desktop and Mobile Devices
Define Cloud COMPUTING
Computational Service as a UTILITY - Enables companies to consume computational resources (virtual machines, storage, application services, etc) as a utility, like we do electricity, rather than having to build and maintain hardware and supporting software infrastructure in-house/on-prem.
Define the role of a Cloud PROVIDER and the advantages they provide and problems they solve?
They are the owners of the data centers who manage and secure those servers, networking, virtualization of hardware and environment.
- Solves lot of problems with scalability and availability as-needed.
- All resources are pulled together and made available to multiple clients who utilize those services
- Users simply choose the service/resource they want and pay per unit of usage
- Services are provided near instantly on-demand.
What are some Azure examples of CapEx?
Azure Reserved VMs or any other Resource or Service where you pay to RESERVE it for future use
What are some Azure examples of OpEx?
Any Service or Resource you provision and can use immediately (non-reserved)
What is Rapid Elasticity? What does it help control?
Because you can Scale Up/Down, Cloud Services are said to be “rapidly elastic” as you can scale up as needed (for a short term client or short term traffic increase, etc.),
Scale Up/Scale out options that you can set to help control COSTS
Set auto Scale Up/Down when usage reaches a certain point. then once that temporary instance is no longer a consideration, you can immediately scale down
What three (3) responsibilities define RELIABILITY?
High Availability - Protects against hardware or software failures
Disaster Recovery - Recovering from natural or human disasters like earth quakes, fire, flooding, terrorist attacks, etc.
Fault Tolerance - Similar to HA but offers ZERO downtime (ability to be up and running immediately eg Instant High Availability)