Tagged articles
8 articles
Page 1 of 1
JavaEdge
JavaEdge
Dec 8, 2024 · Backend Development

Netflix’s Service‑Level Priority Load Shedding: Protecting User‑Initiated Requests

This article explains how Netflix extended its priority load‑shedding strategy from the API gateway to individual services, detailing the classification of user‑initiated versus pre‑fetch requests, the implementation of partitioned concurrency limiters, CPU‑ and I/O‑based shedding, test results, and real‑world impact on availability.

Backend ArchitectureNetflixconcurrency limits
0 likes · 18 min read
Netflix’s Service‑Level Priority Load Shedding: Protecting User‑Initiated Requests
Tencent Cloud Middleware
Tencent Cloud Middleware
Apr 4, 2023 · Backend Development

Why Kafka’s High Reliability and Performance Matter for Asynchronous Decoupling and Load Smoothing

This article explains Kafka’s core concepts, architecture, and the mechanisms—such as ACK policies, replication, HW/LEO management, zero‑copy I/O, batching, compression, and load‑balancing—that together ensure high reliability and high throughput for asynchronous decoupling and peak‑shaving scenarios.

Kafkaasynchronous decouplinghigh performance
0 likes · 33 min read
Why Kafka’s High Reliability and Performance Matter for Asynchronous Decoupling and Load Smoothing
DevOps
DevOps
May 18, 2022 · Operations

Understanding and Preventing Cascading Failures in Distributed Systems

The article explains how cascading failures arise from positive feedback loops in distributed systems, illustrates real‑world incidents such as the 2015 DynamoDB outage, outlines anti‑patterns like unlimited retries and unchecked load, and presents practical mitigation techniques including load‑shedding, circuit breakers, exponential back‑off, and controlled replication to improve system resilience.

Distributed SystemsResilienceSRE
0 likes · 19 min read
Understanding and Preventing Cascading Failures in Distributed Systems
Big Data Technology & Architecture
Big Data Technology & Architecture
Jul 15, 2019 · Backend Development

Why Use Message Queues? Benefits, Drawbacks, and Comparison of Kafka, ActiveMQ, RabbitMQ, and RocketMQ

The article explains why message queues are employed for decoupling, asynchronous processing, and load‑shedding, outlines their advantages and disadvantages, and compares popular MQ products such as Kafka, ActiveMQ, RabbitMQ, and RocketMQ to guide technology selection.

AsynchronousBackend ArchitectureDecoupling
0 likes · 5 min read
Why Use Message Queues? Benefits, Drawbacks, and Comparison of Kafka, ActiveMQ, RabbitMQ, and RocketMQ
WeChat Backend Team
WeChat Backend Team
Jan 17, 2019 · Operations

How We Built DAGOR: A Scalable Overload Control System for Massive Microservices

This article presents DAGOR, a decentralized overload control framework designed for large‑scale microservice architectures like WeChat’s backend, detailing its service‑agnostic design, priority‑based admission policies, adaptive algorithms, and experimental evaluation that demonstrates improved success rates, fairness, and robustness under heavy load.

MicroservicesScalable Systemsload shedding
0 likes · 49 min read
How We Built DAGOR: A Scalable Overload Control System for Massive Microservices
Qunar Tech Salon
Qunar Tech Salon
Apr 19, 2017 · Backend Development

Rate Limiting Strategies for API Services: Design, Implementation, and Load Shedding

This article explains why availability and reliability are critical for web APIs, outlines four common rate‑limiting techniques used at Stripe, describes how to choose and implement request, concurrent, usage‑based, and worker‑utilization limiters, and provides practical guidance for safely deploying them in production.

APIOperationsToken Bucket
0 likes · 11 min read
Rate Limiting Strategies for API Services: Design, Implementation, and Load Shedding
High Availability Architecture
High Availability Architecture
Apr 6, 2017 · Backend Development

Four Common API Rate Limiting Strategies and Their Implementation at Stripe

This article explains why availability and reliability are essential for web APIs, outlines four common rate‑limiting approaches used by Stripe—including request, concurrent, usage‑based, and worker‑utilization limiters—and provides practical guidance on implementing token‑bucket limiters with Redis while ensuring safe error handling and gradual rollout.

APIStripeToken Bucket
0 likes · 9 min read
Four Common API Rate Limiting Strategies and Their Implementation at Stripe
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Oct 11, 2016 · Operations

How to Gracefully Degrade Services When Server Load Spikes

This article explains various service degradation strategies—including interface and page refusal, delayed persistence, and persistent‑layer restrictions—along with management approaches and implementation points such as middleware control, NGINX+LUA page blocking, and data‑operation rules, to keep core functions running under high server pressure.

Operationsasynchronous queuecaching
0 likes · 4 min read
How to Gracefully Degrade Services When Server Load Spikes