This article explains the fundamentals of message queues, describing how MQ, Kafka, and RocketMQ handle asynchronous processing, traffic shaping, and decoupling through topics, partitions, consumer groups, and storage mechanisms such as sequential writes and page‑cache optimization.
This article introduces the concept of message queues, explains their role in decoupling systems and improving performance, compares point‑to‑point and publish/subscribe models, and provides an overview of JMS, RabbitMQ, AMQP, and Kafka with practical examples and diagrams.
Shopee Shake’s architecture separates admin and user sides into three layers—access, application, and resource—and uses horizontal scaling, bucketed Redis coin pools, multi‑level caching, asynchronous message queues, precise capacity formulas, and comprehensive monitoring and chaos‑engineered runbooks to reliably handle over 300,000 QPS during major promotional events.
The article examines Kuaishou Y‑tech's server‑side effects platform, detailing its background, technical challenges, exploration of open‑source workflow and serverless frameworks, architectural adjustments for non‑blocking APIs, and future development directions while highlighting recruitment opportunities.
This article examines the challenges of implementing a flash‑sale (秒杀) system—such as overselling, massive concurrency, request flooding, URL exposure, and database strain—and presents a comprehensive backend design that includes dedicated databases, dynamic URLs, static page rendering, Redis clustering, Nginx load balancing, optimized SQL, token‑bucket rate limiting, asynchronous order processing, and service degradation strategies.
The article explains Facebook’s Ordered Queue Service (FOQS), a multi‑tenant distributed priority queue that supports asynchronous job processing for services like Async, video encoding and translation, detailing its architecture, Thrift API, enqueue/dequeue mechanisms, ack/nack handling, scaling practices, checkpointing and disaster‑recovery strategies.
This article provides a comprehensive overview of message queues, explaining their purpose, usage scenarios, two communication models, and detailing Java Message Service (JMS) as well as popular MQ implementations such as RabbitMQ and Kafka, complete with diagrams and code examples.
This article explains the fundamentals of message queues, their role in asynchronous processing and system decoupling, introduces Java Message Service (JMS), compares point‑to‑point and publish‑subscribe models, and provides an overview of common MQ implementations such as RabbitMQ and Kafka.
This article explains the drawbacks of traditional synchronous request handling, introduces message queues as a solution for asynchronous processing, decoupling services, and traffic shaping, and then details the common MQ challenges—duplicate messages, data inconsistency, loss, ordering, backlog, and added system complexity—along with practical mitigation strategies.
This article details Ximalaya's evolution of its HTTP gateway—from a Tomcat NIO prototype to a fully asynchronous Netty design—covering architectural diagrams, performance bottlenecks, traffic management features, monitoring, GC tuning, and future plans for HTTP/2 and graceful degradation.
This article introduces RabbitMQ, explains its core concepts and typical scenarios such as decoupling, asynchronous processing, and traffic shaping, and discusses the benefits and challenges of integrating a message queue into backend architectures.
This article explains the role of message queues in asynchronous processing, application decoupling, traffic shaping and log handling, compares popular MQ products, details RabbitMQ concepts and common patterns, and discusses reliability, ordering, dead‑letter, TTL and clustering strategies.
This article explores the key challenges of designing a flash‑sale (秒杀) system—such as overselling, high concurrency, request flooding, and database strain—and presents a comprehensive backend architecture with database design, dynamic URLs, caching, rate limiting, async ordering, and service degradation techniques.
The article explains how increasing business complexity and throughput demands drive system splitting, architectural evolution, and the adoption of scaling, sharding, caching, and asynchronous messaging techniques to improve capacity, robustness, and maintainability of large‑scale backend services.
This article explains the fundamentals of message‑queue middleware, outlines key scenarios such as asynchronous processing, application decoupling, traffic shaping, log handling and messaging, compares popular products like ActiveMQ, RabbitMQ, ZeroMQ and Kafka, and details JMS concepts and programming models.
This article examines the challenges of building a flash‑sale (秒杀) system—such as overselling, high concurrency, request flooding, URL security, and database strain—and presents a comprehensive backend design using separate databases, Redis clustering, dynamic URLs, static pages, Nginx, rate‑limiting, asynchronous order processing, and service degradation strategies.
This article explains the advantages and disadvantages of using message middleware in microservice architectures and details practical solutions for handling concurrency, ordered processing, duplicate messages, and transactional messaging using patterns like partitioning, outbox tables, CDC, and RocketMQ's two‑phase commit.
This article examines the challenges of building a flash‑sale (秒杀) system—such as overselling, high concurrency, request throttling, and database strain—and presents a comprehensive backend design using separate databases, dynamic URLs, static pages, Redis clustering, Nginx, token‑bucket rate limiting, asynchronous order processing, and service degradation strategies.
The article details how Didi’s large‑scale Ceph deployment suffered from high tail latency due to long‑held and coarse‑grained locks, and describes a series of fixes—including asynchronous read threads, fine‑grained object caches, per‑thread lock‑free logging, and lock‑free filestore apply—that cut latency by up to 90 % and more than doubled read throughput.
This article presents a comprehensive guide to designing high‑concurrency architectures for e‑commerce applications, covering server topology, load balancing, database clustering, caching strategies, concurrency testing tools, message‑queue based asynchronous processing, first‑level cache, static data handling, layering, distribution, service‑oriented design, redundancy, automation, and practical implementation examples.
This article explains the real‑world origin of message queues, illustrates how they enable asynchronous processing, traffic control, and service decoupling, and compares their benefits and drawbacks with concrete examples such as flash‑sale systems and token‑bucket flow control.
This article explains the role of message‑queue middleware in distributed systems, covering its core functions, common use cases such as asynchronous processing, application decoupling, traffic shaping, log handling and messaging, and provides concrete architectural examples illustrating performance improvements and design patterns.
This article explains the role of message queues in distributed systems, illustrates four typical scenarios—asynchronous processing, application decoupling, traffic shaping, and message communication—and compares the features of popular middleware such as ActiveMQ, RabbitMQ, RocketMQ, and Kafka.
This article introduces the fundamentals of message queues, explains their characteristics, delivery models, transmission modes, and push‑pull patterns, then compares four popular implementations—ActiveMQ, RabbitMQ, RocketMQ, and Kafka—highlighting each system's strengths, weaknesses, deployment requirements, and typical use cases.
This article examines the challenges of building a flash‑sale (秒杀) system—such as overselling, massive concurrent requests, URL exposure, and database overload—and presents a comprehensive backend architecture that leverages Redis clustering, dynamic URLs, Nginx load balancing, rate‑limiting, asynchronous order processing, and service degradation techniques to achieve robust, scalable performance.
This article explains the role of message‑queue middleware in distributed systems, describes common use cases such as asynchronous processing, application decoupling, traffic shaping, log handling and messaging, and provides an overview of popular brokers and the JMS programming model.
This article explains the role of message‑queue middleware in distributed systems, covering its communication patterns, ten key advantages such as decoupling and scalability, and practical use cases like asynchronous processing, traffic shaping, log handling, and e‑commerce architectures.
This article explains the fundamental properties of message queues, why they are needed, the advantages they bring such as improved response speed, stability, and decoupling, and discusses distributed system challenges and practical implementation considerations for selecting and deploying a suitable message‑queue solution.
This guide explains how to set up ThinkPHP5's built‑in Queue component with a Redis driver, create a custom queue class, configure the queue, produce messages, and run a consumer process, including handling retries, delays, and daemon mode.
This article explains the motivations behind MaFengWo's custom message bus, details its architecture and implementation—including SDK, RabbitMQ broker, Go Deliver service, and MySQL subscription storage—and outlines future plans for productization and micro‑service integration.
This article shares Meituan's practical performance‑optimization techniques—including code analysis, database tuning, caching strategies, asynchronous processing, JVM adjustments, multithreading, and monitoring—illustrated with real case studies that reduced job runtimes from over 40 minutes to under 15 minutes.
This article describes how JD's open gateway handles billions of requests during major sales events by employing a multi‑layer architecture, Nginx + Lua unified access, NIO asynchronous processing, service isolation, dynamic routing, degradation, rate‑limiting, circuit‑breaking, fast‑fail mechanisms, and comprehensive monitoring to ensure high performance and reliability.
This article introduces message queue middleware, explains its role in distributed systems for asynchronous processing, system decoupling, traffic shaping, log handling and message communication, and provides concrete e‑commerce and log‑collection examples illustrating how queues improve performance, scalability and reliability.
This article explains how message queue middleware improves distributed systems by enabling asynchronous processing, decoupling services, handling traffic spikes, aggregating logs, and supporting various communication patterns, illustrated with real‑world e‑commerce and logging architectures that boost throughput and reliability.
The article presents Hermes, Meituan’s O2O performance management platform for travel, detailing its six‑module, four‑engine architecture—including data, incentive, rule, calculation, and scheduling engines—while highlighting technical innovations such as two‑level caching, work‑stealing producer‑consumer processing, Map‑Reduce‑style calculations, and future AI‑driven enhancements.
This article introduces Celery, a flexible Python distributed task queue, explains its architecture—including broker, beat, worker, and result backend—then provides a complete, step‑by‑step setup using RabbitMQ and Redis, covering installation, configuration, task definition, worker launch, custom exchanges, and queue routing.
This article describes the design and implementation of a five‑layer one‑stop fund processing platform, covering architecture, rapid business support, hotspot data handling, storage optimization, and query improvements, including sharding, asynchronous processing, and dynamic data source strategies to ensure scalability and reliability.
The article examines the upgrade to a balance‑based financial accounting system, defines hotspot accounts, explains why they pose concurrency challenges, and evaluates several technical solutions—including optimistic locking, asynchronous processing, and account splitting—to guide appropriate strategy selection for different business scenarios.
This article tells the story of a developer who first used a blocking email call, then switched to multithreading, and finally adopted a message queue to achieve asynchronous processing, decoupling, scalability, and reliability for user registration emails.
This article explains the design and improvements of WeChat's MQ 2.0 asynchronous queue, covering its cross‑machine consumption model, enhanced task scheduling, MapReduce‑style processing, stream tasks, and robust overload protection that together enable high‑performance, resilient backend services.
This article outlines a comprehensive approach to building high‑concurrency web systems by introducing layered architecture, modular segmentation, distributed deployment, server clustering, asynchronous processing with message queues, caching strategies, service‑oriented design, and automated redundancy to achieve high availability and scalability.
The article details the QQ Game Spring Festival Red Packet backend, describing its multi‑phase architecture that handles 80 k RPS, uses CDN‑served static gift data, two‑level sorting, CMEM caching, RocketMQ buffering for throttled delivery, idempotent order tracking for fault tolerance, and unified real‑time monitoring.
The article describes how Hujiang built and iterated a three‑generation asynchronous task scheduling platform—Juice—using Mesos and Docker to achieve on‑demand resource allocation, horizontal scalability, and efficient handling of large multimedia processing workloads.
The article outlines the complex business logic of JD Daojia's transaction system and presents architectural decisions such as service setization, database sharding, frontend‑backend separation, parallel execution, asynchronous processing, dependency governance, and future enhancements to improve scalability, reliability, and performance.
The article details the technical challenges encountered during the service‑oriented decomposition of Qunar's payment platform, covering Dubbo and HTTP service conventions, database sharding and read/write separation, asynchronous processing, multi‑system management, and comprehensive monitoring and alerting solutions.
This article explains how queues—such as message queues, task queues, and data‑bus queues—are applied in backend systems for asynchronous processing, system decoupling, data synchronization, traffic shaping, buffering, and other architectural patterns to improve scalability and reliability.
The article examines the technical challenges encountered during the service‑oriented decomposition of Qunar's payment platform—including development efficiency, interface conventions, concurrency, security, monitoring, database sharding, read‑write separation, and asynchronous processing—and presents concrete solutions and best‑practice recommendations.
This article shares Tencent’s experience building fault‑tolerant mechanisms for the AMS activity platform, covering retry strategies, automatic machine exclusion, timeout tuning, service isolation, asynchronous processing, anti‑replay safeguards, and operational best practices that transformed a million‑request service into an 800‑million‑request system.
This article explains the fundamentals of message queue middleware, outlines common scenarios such as asynchronous processing, application decoupling, traffic shaping, logging, and communication, and provides concrete examples and architectural diagrams illustrating how queues improve performance, scalability, and reliability in distributed systems.
This article provides a comprehensive overview of message queues, covering their core concepts, key application scenarios such as asynchronous processing, system decoupling, traffic shaping, log handling, and communication, and examines popular middleware like ActiveMQ, RabbitMQ, ZeroMQ, and Kafka, along with JMS models and programming details.
The article examines the fundamentals of message‑based distributed architecture, explains core messaging patterns such as Message Channel, Publisher‑Subscriber and Message Router, and provides practical application scenarios, technology‑selection criteria, and challenges for building robust enterprise integration solutions.
This article breaks down the three main paths of a user’s request to a large website—browser, network, and server—explains where bottlenecks occur, and offers practical optimization techniques such as DNS prefetching, caching, asynchronous processing, and bandwidth planning, while also defining performance metrics and testing methods.
The 2015 Beijing QCon highlighted four technical talks covering asynchronous processing in distributed systems, the DRC data‑replication infrastructure, minute‑level high‑availability fault recovery, and cloud‑era database operations, illustrating Alibaba's approaches to scalability and reliability in modern cloud platforms.
