Live Streaming Service Overload Incident Caused by Self-Referencing Push Configuration

A sudden surge in live‑stream traffic overloaded the core streaming service because a push configuration mistakenly pointed to the same stream URL, creating a self‑referencing loop that repeatedly generated duplicate streams until the service capacity was exhausted.

backend bugincident analysislive streaming

0 likes · 4 min read

Live Streaming Service Overload Incident Caused by Self-Referencing Push Configuration

Architecture Digest

Jun 19, 2016 · Backend Development

Preventing and Recovering from Service Overload Caused by Cache Failures

This article analyzes how introducing caches can cause service overload, examines five cache get patterns, and proposes prevention, recovery, and flow‑control strategies for both client and server sides to ensure system stability.

CacheDistributed SystemsFlow Control

0 likes · 20 min read

Preventing and Recovering from Service Overload Caused by Cache Failures

Meituan Technology Team

Jun 17, 2016 · Operations

How to Prevent and Recover from Cache‑Induced Service Overload

Service overload caused by cache failures can cripple dependent systems, but by adopting smart cache get patterns, proactive client‑side checks, traffic throttling, service degradation, and dynamic scaling, developers can both prevent overload and recover gracefully when it occurs.

BackendCacheOperations

0 likes · 22 min read

How to Prevent and Recover from Cache‑Induced Service Overload