How Service Degradation Keeps E‑commerce Platforms Stable During Traffic Surges

Why Use Service Degradation

During large events like 618 sales or Double‑11, system pressure spikes dramatically, making availability and stability paramount. Non‑essential functions can be temporarily disabled through degradation, freeing resources for core services. For example, recommendation services during order placement can be paused to prioritize transaction processing.

Dimensions of Service Degradation

(1) Page Degradation – If the order success page fails, redirect users to the order center where they can view and manage orders; if the order center is also unavailable, redirect to the order detail page.

(2) Business Function Module Degradation – Real‑time price queries can be relaxed to less frequent updates; dynamic homepage content generated by heavy computations can be replaced with pre‑prepared static pages during peak traffic, sacrificing freshness for usability.

(3) Remote Service Degradation – Third‑party logistics services that become overloaded can be temporarily bypassed, with calls resumed once the service recovers.

Implementation of Service Degradation

(1) Manual Implementation – Configure toggle switches for degradable services; before major events, identify services to downgrade and turn off their switches in advance.

(2) Automatic Implementation – Degrade automatically when a service call fails or when response time exceeds a predefined threshold, restoring the service once it becomes healthy again.