When designing a highly available ECS networking solution for an e-commerce platform, which features should be included to handle peak loads efficiently?

Question

Options

• ACross-Zone Load Balancing
• BSticky Sessions for user session persistence
• CSingle instance types for cost saving
• DAuto Scaling groups to adjust compute capacity

• A
  83% (19)
• C
  17% (4)

Explanation

Cross-Zone Load Balancing (A) distributes traffic evenly across ECS tasks in multiple Availability Zones, preventing hotspots during peak load and ensuring no single zone becomes a bottleneck. Sticky Sessions (B) bind a user's requests to the same backend instance, which is critical for e-commerce cart and session state continuity without requiring a separate session store. Auto Scaling groups (D) dynamically add or remove ECS capacity in response to traffic spikes, making them essential for handling unpredictable peak loads cost-effectively.

Option C is wrong because using single instance types reduces flexibility and resilience - diverse or appropriately sized instance types allow better cost-performance tuning, and a single type creates a single point of failure if that instance family has capacity constraints in AWS.

Memory tip: Think "LAS Vegas" - Load balance across zones, Auto Scale for demand, Sticky sessions for shoppers. These three together cover distribution, elasticity, and user experience - the three pillars of HA e-commerce architecture.

No community discussion yet for this question.