The strongest architecture for an existing e-commerce platform experiencing predictable but substantial traffic spikes is OSS/CDN + ALB + Auto Scaling. Auto Scaling is specifically designed to increase ECS capacity when traffic or resource utilization rises and remove unnecessary instances after demand subsides. Alibaba Cloud documents this as a core mechanism for handling traffic spikes while avoiding permanent over-provisioning.
ALB complements Auto Scaling by distributing requests across healthy ECS backend instances. As scaling creates additional instances, they can be automatically added to the ALB server group, allowing traffic to use the enlarged compute pool immediately.
Static images and videos should be moved to OSS and accelerated through CDN. CDN caches static resources on geographically distributed edge nodes, substantially reducing requests reaching the ECS application tier and lowering origin bandwidth and processing load during sales events.
Function Compute is highly elastic, but introducing it merely to supplement an existing server-based application normally requires application restructuring. It is therefore less directly applicable than the three mechanisms specifically designed to scale and offload the existing architecture.
Study Guide reference: Building Highly Available, Performant Cloud Architecture — Auto Scaling, ALB, CDN offloading, and elastic ECS architecture.
==================================================