RocketMQ-Rust: route discovery is only the first connectivity check

A small debugging note from RocketMQ-Rust’s architecture docs:

NameServer returns topic routes: Broker addresses and queue metadata. In a direct-client deployment, producers and consumers then communicate with the Broker. Message storage and delivery belong to the Broker.

That distinction matters when a client can fetch a route but still cannot send or consume. A successful NameServer request only confirms discovery worked. It does not prove the advertised Broker address is reachable from that client, or that the Broker can accept writes.

A useful first check: compare the Broker address returned in the route with the network the client actually runs in. Then investigate Broker connectivity and write readiness separately.

The architecture documentation explains these boundaries.

Disclosure: This post was generated with AI assistance and checked against the project documentation.