Compute Services on the Cloud
- Whenever we need virtual servers to run our server side software we use Compute Services
- A Compute service in a cloud offers
- virtual machines
- Runtime/Platforms
- Serverless
Virtual Machine
- Virtual Machine => This is a virtual server where it has the following but still behaves like a physical server
- virtual cpu
- virtual ram
- virtual disk
- An operating system installed
- We are not responsible for
- Physical Network
- Physical Server
- But we are responsible for
- Operating system
- Installing Platforms/Runtime
- Applications
- Data
- This is referred as Infrastructure as a Service (IaaS).
- Machine size => CPU + RAM
- Operating System
- Pricing:
- Machine Size
- OS Costs
- Disk Costs
- Networking (IP)
- We pay in hourly units
Platforms/Runtimes
- In this cases, cloud offers you the preinstalled Runtime (Container) where you can directly run your application
- We get
- Java runtimes
- python runtime
- docker runtime
- dotnet runtime
- …
- …
- This is referred to as Platform as a service
- We run in hourly units
Serverless
- We can run smaller units of code written as functions
- Pricing model of this, you will be paying only when your code is executing.
- min unit is micro seconds to seconds
Where do you want to run (Global Infrastructure of Cloud)
- Cloud Physical Infrastructure:
- Generally all the clouds identify a geographical location where they want to run infrastructure and this referred as Region.
- In a Geographical location i.e. Region they identity atleast 3 different locations which are referred as Zones (Availability Zone) with 30-60 kms far away from each other.
- AWS uses Region with AZ’s
- Azure we have
- Regions with Zones
- Regions without Zones
- In addition to Regions we have
- Edge Locations ( Point of presence)
- Local Zones (AWS)
