compute options
The main ways to run code in the cloud: virtual machines, containers and functions, each moving a different amount of work to the provider.
In more detail
Machines give the most control and the most operational work; containers standardise packaging and let a scheduler place copies; functions remove hosts for bounded, event-driven work. Each choice moves a failure mode somewhere else, so write down which one you accepted.
Related terms
- Amazon EC2 — Amazon Elastic Compute Cloud, the AWS service that rents out virtual servers called instances.
- Amazon ECS — Amazon Elastic Container Service, the AWS-native service that runs and keeps containers running on EC2 or Fargate.
- AWS Lambda — The AWS service that runs a piece of code, called a function, each time an event arrives, with no servers for you to manage.
- decision record — A short written note of a technical decision, the facts behind it and the trade-off accepted, so later reviewers understand why.
Taught in
- Load Balancing and DNS — Cloud Infrastructure & Hyperscaler Architecture
- Serverless Compute (Lambda) — Cloud Infrastructure & Hyperscaler Architecture
- Comparing Compute Options — Cloud Infrastructure & Hyperscaler Architecture
- Infrastructure as Code (Handover to Terraform) — Cloud Infrastructure & Hyperscaler Architecture