Tagged articles
message middleware
16 articles · Page 1 of 1

Niu LiuSep 21, 2026 · Backend Development
The article analyzes priority messaging in message middleware, comparing implementations across RocketMQ, RabbitMQ, Kafka, and Pulsar, and details techniques like weighted round-robin scheduling, resource reservation, and wait aging to ensure urgent tasks get priority without starving ordinary tasks, including practical code patterns for fair task scheduling.
KafkaPulsarRabbitMQ
0 likes · 10 min read

The article details how vivo’s Internet Middleware Team migrated from RabbitMQ to RocketMQ and introduced a user‑property‑based multi‑version isolation layer that tags messages, filters them by consumer groups, and provides fallback and retry mechanisms, enabling test‑environment separation without SDK changes, though offline consumers may miss baseline messages.
Message QueueMulti-Version IsolationRocketMQ
0 likes · 12 min read

This article explains what message middleware is, outlines its key use cases such as asynchronous communication and decoupling, details core principles and models like point‑to‑point and publish/subscribe, reviews popular solutions (Kafka, RabbitMQ, RocketMQ, Pulsar, etc.), and offers selection guidance.
KafkaPulsarRabbitMQ
0 likes · 8 min read

vivo’s Internet Storage team details how it operates RocketMQ for low‑latency online services and Kafka for massive big‑data pipelines, outlines resource isolation, traffic balancing, intelligent throttling, and governance practices, and describes its migration from RabbitMQ and planned shift from Kafka to cloud‑native Pulsar.
KafkaPulsarRocketMQ
0 likes · 22 min read

vivo’s Internet Middleware Team replaced its RabbitMQ service with a RocketMQ‑based platform, building an AMQP‑Proxy gateway and metadata layer to enable seamless, zero‑downtime migration while achieving over 100,000 TPS, billion‑message capacity, 50% resource savings, and advanced features such as transactions, ordered and delayed messaging, and tracing.
RabbitMQ MigrationRocketMQdistributed systems
0 likes · 12 min read

This article compares Pulsar with Kafka, RocketMQ and InLong‑TubeMQ, focusing on cloud‑native multi‑tenant design, multi‑level flow control, compute‑storage separation, partitioning strategies, metadata storage, and message delivery mechanisms, highlighting each system's architectural advantages and trade‑offs.
InLong‑TubeMQKafkaMulti‑tenant
0 likes · 18 min read

This article walks through the step‑by‑step architectural evolution of a Java Web e‑commerce platform, covering initial single‑machine deployment, separation of application and database servers, clustering, load‑balancing algorithms, session handling, read/write splitting, search integration, caching, database sharding, microservice decomposition, SOA governance, and the introduction of message middleware.
CachingJavamessage middleware
0 likes · 16 min read

The article explores how enterprises can reduce tight coupling in microservice architectures by converting synchronous calls to asynchronous messaging, adopting message‑oriented middleware, applying event‑driven analysis, and leveraging CQRS patterns, while also offering practical refactoring tactics for overly coupled services.
Decouplingasynchronouscqrs
0 likes · 20 min read

ZMS is ZTO Express's cloud‑native message middleware platform built on RocketMQ and Kafka that automates deployment, provides a unified SDK, supports multi‑datacenter operation, and offers comprehensive monitoring, enabling seamless scaling and fault‑tolerant messaging for billions of daily events.
OperationsRocketMQcloud‑native
0 likes · 8 min read

This article explains how database sharding in micro‑service architectures creates transaction consistency problems and demonstrates a RocketMQ‑based solution that uses a two‑phase message workflow, state checks, and a Transaction table to achieve reliable distributed transactions.
RocketMQTransaction Consistencydistributed transaction
0 likes · 8 min read

The article explains how engineers can design robust game special‑event systems by abstracting features into reusable components, applying hook‑based extensibility, and using asynchronous message middleware to handle diverse, time‑critical, high‑risk operations, illustrated with the 37 Platform’s event architecture and configuration‑driven flexibility.
Redishooksmessage middleware
0 likes · 9 min read

Message-oriented middleware (MOM) enables reliable, asynchronous communication between distributed applications, reducing coupling and enhancing scalability, with JMS providing a platform-independent API for producers, consumers, queues, and topics, and various implementations such as ActiveMQ, RocketMQ, and RabbitMQ offering diverse messaging solutions.
asynchronous communicationjmsmessage middleware
0 likes · 5 min read

This article introduces the fundamentals of message middleware, explains its key application scenarios such as asynchronous processing, system decoupling, flow control, and distributed transaction consistency, details the three transmission modes (point‑to‑point, publish/subscribe, request‑reply), and provides a step‑by‑step ActiveMQ quick‑start guide with Spring Boot integration and complete Java code examples.
ActiveMQJavaSpring Boot
0 likes · 19 min read

This article explains the core concepts, component diagram, message flow, cross‑center sequencing, high‑availability design, and detailed ActiveMQ configuration for OneMM message‑oriented middleware, highlighting how asynchronous and decoupled communication improves system efficiency and scalability.
ActiveMQDecouplingasynchronous
0 likes · 15 min read

The article explains the widespread use of message oriented middleware, outlines its core challenges such as synchronous vs. asynchronous delivery, security, persistence, redelivery, ordering, and describes the two main transmission models—point‑to‑point and publish/subscribe—while comparing JMS and AMQP standards.
AMQPMOMjms
0 likes · 6 min read


21CTOJul 25, 2017 · Fundamentals
This article explains distributed system fundamentals—CAP theorem, ACID properties, consistency models, and how 2PC and 3PC protocols, along with message‑middleware solutions like RocketMQ, address the challenges of achieving reliable complex distributed transactions.
2PC3PCACID
0 likes · 14 min read
