- Auto Scaling (broader than just EC2)
- Offloading and load distribution (caching, proxies, read replicas, CDNs)
- Serverless choices that reduce operational overhead and simplify scaling
Auto Scaling — not just for EC2
Auto Scaling is commonly associated with EC2 Auto Scaling groups, but the concept and tooling extend far beyond instances. Many AWS services provide automated scaling (via Application Auto Scaling, service-managed autoscaling, or serverless autoscaling), so you don’t have to manage capacity manually. When comparing manual scaling with Auto Scaling in a design or exam question, prefer AWS-managed or automatic scaling when it meets requirements—especially for hosting platforms and managed databases. Services that support autoscaling patterns include EC2, ECS, Fargate, Lambda, Aurora, DynamoDB, ElastiCache, Keyspaces, Neptune, DocumentDB, and managed Kafka offerings.
- EC2 Auto Scaling uses Auto Scaling groups and policies (target tracking, step scaling, scheduled scaling).
- Many managed services offer autoscaling that’s configured for you (serverless) or configurable via Application Auto Scaling.
- For exam scenarios that require low operational overhead and reliable scaling, select the managed/autoscaled option if constraints (latency, custom OS, stateful needs) permit.
Offloading and Load Distribution
Offloading moves specific work away from your primary system into specialized components so the core system handles less load. Offloading pairs naturally with load balancers and caching mechanisms. Common offloading patterns:- Use ELB/ALB/NLB to distribute incoming traffic and prevent any single backend node from being a bottleneck.
- Offload static content to S3 and serve it via CloudFront so web servers process only dynamic requests.
- Place proxies or edge logic (NGINX, API Gateway, CloudFront Functions) in front of origins to handle routing, TLS termination, request shaping, or caching.

- Read replicas absorb the majority of read traffic for read-heavy workloads (for example, workloads with 80/20 read/write ratios or similar). Directing reads to replicas reduces load on the primary writer and lets you scale reads independently.
- Some services support multi-master or alternative replication modes—these change routing and conflict-handling behaviors, so always examine the service’s replication model before designing.






Serverless: built-in scaling and lower operational overhead
Serverless services (AWS Lambda, Fargate, Aurora Serverless, Redshift Serverless, EMR Serverless, etc.) shift many operational responsibilities to AWS, including capacity, scaling, and patching. Serverless typically offers:- Automatic, fine-grained scaling per request or per workload
- Minimal operational overhead compared to maintaining Auto Scaling groups and server fleets
- Cost benefits for spiky or unpredictable workloads (pay-per-use)

Summary and exam guidance
This lesson emphasized three performance-focused strategies:- Auto Scaling — Autoscaling is available across many AWS services (not only EC2). Prefer autoscaling when the service supports it and the use case allows.
- Offloading and load distribution — Use load balancers, caches, read replicas, and CDNs to separate concerns and reduce load on primary systems (e.g., reads vs writes, static vs dynamic content).
- Serverless — Choose serverless to reduce operational overhead and gain automatic, per-request scaling when it satisfies the application constraints.
- If an option offers autoscaling and another requires manual scaling, prefer the autoscaled option when it meets the requirements.
- If you can offload reads, caching, or static content and that meets functional requirements, offloading usually yields better performance.
- If multiple answers meet the requirements and one is serverless while the others are server-based, favor the serverless option from an AWS best-practices perspective (only if it meets constraints).
Exam tip: Look for options that reduce operational overhead and improve automatic scaling—managed autoscaling and serverless options are often the correct choice when they meet the requirements.
Links and references
- AWS Well-Architected Framework — Performance Efficiency Pillar
- Amazon EC2 Auto Scaling Documentation
- Amazon Aurora — Read Replicas and Cluster Concepts
- Amazon ElastiCache Documentation
- Amazon CloudFront Documentation
- AWS Lambda — Serverless Compute