Common cloud services Flashcards
Four most common types of cloud services for IaaS would be:
Compute:
Imagine having a virtual computer that can run applications, programs and code.
Storage:
This is where you would have a virtual hard-drive that can store files.
Networking:
Virtual network being able to define internet connections or network isolations
Databases:
Virtual database for storing reporting data or a database for general perpose web-application.
What is microsoft?
An american multinational computer technology corporation headquarted in redmond, washington.
Makes software, phones, tablets, game consoles, cloud services, a search engine and more!
Best know for their operation system called windows.
Been around since 1970’s
What is Azure?
Microsoft calls their cloud provider service Microsoft Azure
Benefits of clod computing (6)
Cost-effective : You pay for what you consume, no up-front cost. Pay-as-you-go (PAYG)
thousands of customers sharing the cost of the resources
Global : Launch workloads anywhere in the world, just choose a region and you are now in the global market
Secure : Cloud provider takes care of physical security. Cloud services can be secure by default or you have the ability to configure access down to granular level.
Reliable : data backup, disaster recovery, and data replication, and fault tolerance
Scalable : Increase or decrease resources and services based on demand.
Elastic : Automate scaling during spikes and drop in demand
Current : The underlying hardware and managed software is patched, upgraded and replaced by the cloud provider without interruption to you
Types of cloud computing (THE PYRAMID)
Top:
SaaS (Software as a Service) (ex. Salesforce, Gmail, Office 365)
- A product that is run and managed by the service provider.
Don’t worry about how the service is maintained. It just works and remains available
Middle: (makes easy for developers to build apps on the cloud without worrying about the stuff underneath)
PaaS (Platform as a Service) (ex. elastic beanstalk on AWS, heroku, google app engine)
- Focus on the deployment and management of your apps.
Don’t worry about: provisioning configuring or understanding the hardware or OS.
Bottom:
IaaS (Infrastructure as a Service) (ex. Microsoft Azure, AWS, oracle cloud)
- The basic building blocks for cloud IT. Provides access to networking features, computers, and data storage space.
Don’t worry about IT staff, data centers and hardware.
Type of cloud computing responsibilities
Applications
Data
Runtime
Middleware
OS
Virtualization
Servers
Storage
Networking
Put them on the right place
On-Premise
cloud service provider (csp)
customer (cus)
Applications
Data
Runtime
Middleware
OS
Virtualization
Servers
Storage
Networking
IaaS
csp
Virtualization
Servers
Storage
Networking
cus
Applications
Data
Runtime
Middleware
OS
PaaS
csp
Runtime
Middleware
OS
Virtualization
Servers
Storage
Networking
cus
Applications
Data
SaaS
csp
Applications
Data
Runtime
Middleware
OS
Virtualization
Servers
Storage
Networking
cus
Cloud deployment models (public, private, hybrid)
Public cloud
everything built on the cloud provider.
Nothing on prem.
Also known as: Cloud-Native
Private cloud
Everything is built on company’s datacenters
Also known as On-Premise
The cloud could be OpenStack
Hybrid
Using both On-Premise and
A Cloud Service Provider
The are networked togehter!! ExpressRoute!
Total cost of Ownership (TCO)
What does the icebergs look like?
CAPEX (Has more hidden costs)
Software license fees
~~~~~~~~~~~(ice berg, under water)
implementation
Configuration
Training
Physical Security
Harware
IT Personal
Maintenance
OPEX
Subscription fees
~~~~~~~~~~~~~~~~
Implementation
Configuration
Training
Generally one saves 75% when doing OPEX style
CAPTIAL VS OPERATIONAL EXPENDITURE
CAPEX
Spending money upfront on physical infrastructure.
Deducting that expense from your tax bill over time.
Server Costs (Computers)
Storage Costs (hard drives)
Network costs (routers, cables, switches)
Backup and Archive Costs
Disaster recovery costs (maybe an extra power supply)
Datacenter Costs (Rent, Cooling, Physical Security)
Technical Personal
-With capital expenses you have to guess upfront what you plan to spend
OPEX
The costs associated with an on-premise datacenter that has shifted the cost on the service provider.
The customer only has to be concerned with non-physical costs.
Leasing software and customizing features
Training employees in cloud services
Paying for cloud support
Billing based on the cloud metrics eg.
> compute usage
> storage usage
With Operation Expenses you can try a product or service without investing in equipment
Cloud Architecture Terminologies (5)
Availability - Your ability to ensure a service remains available.
Highly Available (HA)
Scalability - Your ability to grow rapidly or unimpeded
Elasticity - Your ability to shrink and grow to meet the demand
Fault tolerance - Your ability to prevent a failure
Disaster recovery - Your ability to recover from a failure
Highly Durable (DR)
High Availability (HA)
Your ability for you service to remain available by ensuring there is *no single point of failure and/or ensure a certain level of performance.
How can you be highly available?
Running your workload across multiple Availability Zones ensures that if 1 or 2 AZ become unavailable your service/applications remains available!!
BUT YOU NEED AN AZURE LOAD BALANCER
What is an Azure Load balancer?
a load balancer allows you to evenly distribute traffic to multiple servers in one or more datacenters. If a datacenter or server becomes unavailable (unhealthy) the load balancer will route the traffic to only available datacenters with servers.
High Scalability
Your ability to increase your capacity based on the increasing demand of traffic, memory and computing power.
Vertical Scaling
- Scaling UP
(Upgrading to bigger servers, bigger hard drives )
Horizontal Scaling
- Scaling OUT
(Adding more servers of the same size)
High Elasticity
The ability to automatically increase or decrease your capacity based on the current demand of traffic, memory and computing power.
(Sounds a lot like high scalability - the difference is that this is automatic and you can increase AND decrease the demand)
usually seen with Horizontal Scaling
(cuz vertical scaling is generally hard for traditional architecture)
Horizontal scaling
Scaling Out - Add servers of the same size
Scaling in - Removing servers of the same size
(usually seen with elasticity)