Design and Technical Specification of a High‑Throughput Message Center
This article presents a comprehensive design for a high‑availability message center that targets 10,000 messages per second inbound throughput and 1,000 messages per second outbound delivery, detailing technical goals, functional requirements, technology selection, architectural diagrams, and implementation guidelines using RocketMQ, Elasticsearch, Spring Cloud Gateway, MySQL, Docker, and Kubernetes.
Technical Goal: Achieve an upstream message‑queue API throughput of 10,000 messages/second and downstream delivery to third‑party platforms of 1,000 messages/second (platform‑internal capacity), while ensuring 100% high availability of the message center.
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 simple message‑template integration (≈5 minutes for basic integration), and standardize message templates.
Functional Requirements: Support third‑party push channels such as Alibaba Cloud SMS, WeChat public account, app push, unified in‑site messages, and Enterprise WeChat (application and personal). Features include message‑template management, account management, message search, and bulk message sending.
Technical Solution Overview:
Business core logic interaction diagram:
Technology Choice
Advantages
Disadvantages
RocketMQ
High performance – single instance can reach 100k msgs/sec; parallel push capability can be scaled via partitions.
Some features not supported – messages in RocketMQ cannot be retracted; certain database‑level functionalities are unavailable.
Elasticsearch
Excellent for billions of records keyword search; real‑time sync performance and throughput are adequate.
Concurrent insert performance is weaker – high‑throughput sync may stress ES; needs testing for capacity limits.
High‑Level Design Description:
RocketMQ: normal message queue for regular delivery, retry queue with multiple delay mechanisms, and result queue for success/failure notifications.
Elasticsearch: synchronize messages from the three queues to maintain eventual consistency via latest timestamp validation.
MySQL: manage templates, accounts, and other basic administrative data.
Underlying Framework and Operations Layer:
Unified gateway: Spring Cloud Gateway or Kong for API‑level routing only.
Base framework: select specific JAR versions; wrap ES, RocketMQ, real‑time alarm, and performance monitoring interfaces; ES supports SQL‑style insert/query; RocketMQ implementation is abstracted. Reference: BSF unified base framework .
Business framework: standard input/output HTTP/RPC utilities and protocol‑level support.
High availability services: Kubernetes & Docker with DevOps for one‑click deployment, rollback, rolling updates, and zero‑downtime releases.
Author: Che Jiangyi – Source: https://www.cnblogs.com/chejiangyi/p/14884931.htm
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.
IT Architects Alliance
Discussion and exchange on system, internet, large‑scale distributed, high‑availability, and high‑performance architectures, as well as big data, machine learning, AI, and architecture adjustments with internet technologies. Includes real‑world large‑scale architecture case studies. Open to architects who have ideas and enjoy sharing.
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.