Skip to content

Apache RocketMQ framework overview prompt

Create a restrained 16:9 editorial architecture illustration for a Chinese source-code guide about Apache RocketMQ 5.5.1. The image is a conceptual summary of the whole framework, not an exact sequence diagram.

Composition:

  • Left zone: Producer, Consumer, gRPC/Proxy clients and Admin Tools as distinct entry roles.
  • Upper middle control plane: NameServer for Topic routing and an optional Controller/DLedger group for Broker master election and SyncStateSet metadata.
  • Center: a Broker cluster with Remoting/Processor, Broker lifecycle orchestration, long polling, transaction service and timer service.
  • Lower middle data plane: one shared CommitLog feeding ConsumeQueue and IndexFile, with a parallel flush and HA replication path; show TieredStore as an optional outer storage extension.
  • Direction: route lookup and control arrows should be visually thinner than the main message data flow. Producer and Consumer data paths must bypass NameServer and connect directly to Broker after routing.
  • External dependencies: JDK/Netty runtime, operating-system PageCache, disk and optional observability stack placed along the outside boundary.

Required Chinese labels: 生产者, 消费者, NameServer 路由, Broker 集群, Remoting 请求分派, CommitLog, ConsumeQueue, 事务回查, 定时投递, Controller 选主, HA 复制, 可选分层存储.

Visual style: light neutral background, charcoal structure, restrained Apache red for the main message flow, teal for route/control flow and amber for delayed/transaction branches. Use square or low-radius nodes, crisp arrows, balanced information density and legible Chinese text. Leave modest clear space for the article title.

Negative constraints: no gradients, no decorative blobs, no dashboard screenshot, no 3D server racks, no benchmark numbers, no invented cloud services, no ZooKeeper on the mandatory RocketMQ data path, no single request enlarged as the whole architecture, and no relationship that contradicts the evidence. The generated image must remain understandable if the article is read without it.

Evidence references: E03, E06, E07, E08, E09, E12.

最后更新:

文章结论绑定 source commit;动态信息以核对日期为准。