2.2. Core AWS Services: Compute
Compute services are the backbone of any application, providing the processing power needed to run code. Think of compute like transportation: EC2 is like owning a car (full control, you drive and maintain it), Lambda is like a taxi (appears when you need it, you pay per ride), and Fargate is like a shuttle service for containers (scheduled runs, no vehicle maintenance). Without the right compute choice, organizations either waste money running idle servers 24/7 or fail to handle traffic spikes — and when your application crashes under load, customers leave and revenue breaks.
💡 First Principle: The First Principle of AWS compute is to provide scalable, flexible, and cost-effective processing power, enabling users to choose the right resource for their application while shifting the burden of infrastructure management to AWS.
Scenario: A company needs to run a web application, a background processing task, and a containerized microservice. They need to choose the appropriate compute service for each.
Reflection Question: How do diverse AWS compute services (e.g., EC2, Lambda, Fargate) fundamentally enable businesses to choose the right processing power for their application while simplifying the management of underlying infrastructure?
