Design of a High‑Throughput Messaging Center Architecture
This article outlines a backend messaging center architecture that targets 10,000 messages per second inbound via RocketMQ, 1,000 messages per second outbound to third‑party platforms, and ensures 100% high availability using Spring Cloud Gateway, Kubernetes, Elasticsearch, and related technologies.
Goal
Technical goal: Achieve an upstream API throughput of 10,000 messages/second to the message queue and deliver 1,000 messages/second to third‑party platforms (the third‑party limit is measured on their side); ensure the message center is 100% highly available.
Business goal: Integrate new requirements, designate the architecture team as the owner of the message center, and provide timely business response and feedback.
Product goal: Support message status queries, provide a simple message‑spec integration (5‑minute integration for junior developers), and standardize message templates.
Requirement Prototype
Functional Requirements
Support third‑party push channels such as Alibaba Cloud SMS, WeChat public account, app push, unified in‑site messages, and Enterprise WeChat (applications and personal). Include message template management, account management, message search, and batch sending.
Technical Solution
Business deployment interaction diagram
Business core logic interaction diagram
Technical Choice
Advantages
Disadvantages
RocketMQ
High performance – single instance can reach 100k msgs/sec; parallel consumption can be scaled via partitions.
Some features not supported – messages in the queue cannot be recalled; certain database‑level capabilities are unavailable.
Elasticsearch
Handles billions of records, fast keyword search, real‑time sync performance.
Concurrent insert performance is weaker; high‑throughput sync may stress ES and require testing.
High‑Level Design Description
RocketMQ: normal message queue (regular delivery), retry queue (supports multiple delay mechanisms for failed messages), and result queue (stores success or limit‑exceeded messages).
Elasticsearch synchronizes the three queues to maintain eventual consistency using the latest timestamp for validation.
MySQL stores only template, account, and other basic management data.
Underlying Framework and Operations Description
Unified gateway: Spring Cloud Gateway or Kong, providing API‑level routing only.
Base framework: selected JAR versions, Elasticsearch, RocketMQ, real‑time alerting, performance monitoring; these interfaces are wrapped for secondary use. ES supports SQL‑style insert/query; RocketMQ implementation is abstracted. Reference: https://gitee.com/yhcsx/csx-bsf-all
Business framework: standard I/O, HTTP, RPC, and other protocol utilities.
High availability: Kubernetes & Docker with DevOps integrated deployment, enabling one‑click release, rollback, rolling updates, and zero‑downtime deployments.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Architect
Professional architect sharing high‑quality architecture insights. Topics include high‑availability, high‑performance, high‑stability architectures, big data, machine learning, Java, system and distributed architecture, AI, and practical large‑scale architecture case studies. Open to ideas‑driven architects who enjoy sharing and learning.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.