BestHub
Sign in
Tagged articles
15 articles
Page 1 of 1
vivo Internet Technology
vivo Internet Technology
Mar 27, 2024 · Backend Development

RocketMQ Multi-Version Environment Isolation Practice in Test Environments

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 MiddlewareMessage QueueMiddleware Architecture
0 likes · 12 min read
RocketMQ Multi-Version Environment Isolation Practice in Test Environments
Mike Chen's Internet Architecture
Mike Chen's Internet Architecture
Jan 17, 2024 · Backend Development

Mastering Message Middleware: From Basics to Choosing the Right Solution

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.

Distributed SystemsKafkaMessage Middleware
0 likes · 8 min read
Mastering Message Middleware: From Basics to Choosing the Right Solution
vivo Internet Technology
vivo Internet Technology
Jan 11, 2023 · Cloud Native

Practices of Distributed Message Middleware at vivo: From RocketMQ to Kafka and Pulsar

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.

Big DataCloud NativeKafka
0 likes · 22 min read
Practices of Distributed Message Middleware at vivo: From RocketMQ to Kafka and Pulsar
vivo Internet Technology
vivo Internet Technology
Jul 27, 2022 · Operations

Building and Migrating to RocketMQ-based Message Middleware Platform at vivo

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.

Distributed SystemsMessage MiddlewareRabbitMQ Migration
0 likes · 12 min read
Building and Migrating to RocketMQ-based Message Middleware Platform at vivo
High Availability Architecture
High Availability Architecture
Oct 28, 2021 · Cloud Native

Design and Implementation Differences between Pulsar, Kafka, RocketMQ, and InLong‑TubeMQ

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.

Cloud NativeInLong‑TubeMQKafka
0 likes · 18 min read
Design and Implementation Differences between Pulsar, Kafka, RocketMQ, and InLong‑TubeMQ
IT Architects Alliance
IT Architects Alliance
Jun 10, 2021 · Backend Development

Evolution of a Java Web E‑commerce System Architecture: From Single‑Server Deployment to Microservices and Distributed Infrastructure

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.

JavaMessage Middlewarecaching
0 likes · 16 min read
Evolution of a Java Web E‑commerce System Architecture: From Single‑Server Deployment to Microservices and Distributed Infrastructure
Architects' Tech Alliance
Architects' Tech Alliance
Feb 19, 2021 · Backend Development

Strategies for Decoupling Microservices: Asynchronous Calls, Message Middleware, Event‑Driven Architecture, and CQRS

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.

AsynchronousCQRSDecoupling
0 likes · 20 min read
Strategies for Decoupling Microservices: Asynchronous Calls, Message Middleware, Event‑Driven Architecture, and CQRS
Zhongtong Tech
Zhongtong Tech
Jun 1, 2020 · Backend Development

How ZTO Express Built ZMS: A Scalable Cloud‑Native Message Middleware Platform

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.

Message MiddlewareOperationsRocketMQ
0 likes · 8 min read
How ZTO Express Built ZMS: A Scalable Cloud‑Native Message Middleware Platform
Java Backend Technology
Java Backend Technology
Sep 24, 2019 · Backend Development

How RocketMQ Solves Distributed Transaction Issues with Message Middleware

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.

Message MiddlewareRocketMQdistributed-transaction
0 likes · 8 min read
How RocketMQ Solves Distributed Transaction Issues with Message Middleware
37 Interactive Technology Team
37 Interactive Technology Team
Nov 28, 2018 · Game Development

Business System Architecture Design: An Engineer's Guide to Game Event Systems

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.

Message MiddlewareSystem Architecturehooks
0 likes · 9 min read
Business System Architecture Design: An Engineer's Guide to Game Event Systems
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Jun 19, 2018 · Backend Development

Understanding Message-Oriented Middleware and JMS: Core Concepts and Benefits

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.

JMSMessage Middlewareasynchronous communication
0 likes · 5 min read
Understanding Message-Oriented Middleware and JMS: Core Concepts and Benefits
Java Captain
Java Captain
May 23, 2018 · Backend Development

Introduction to Message Middleware and ActiveMQ: Scenarios, Transmission Modes, and Spring Boot Integration

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.

ActiveMQJMSJava
0 likes · 19 min read
Introduction to Message Middleware and ActiveMQ: Scenarios, Transmission Modes, and Spring Boot Integration
Architecture Digest
Architecture Digest
Sep 19, 2017 · Backend Development

Key Challenges and Transmission Models of Message Oriented Middleware (MOM)

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.

AMQPJMSMOM
0 likes · 6 min read
Key Challenges and Transmission Models of Message Oriented Middleware (MOM)