Designed the broker-side topology for the new background queue — direct exchange, a work queue with a routing key, and a separate failure queue on the same virtual host — and validated the option shapes against the client transport without ever connecting, since neither broker nor client extension was reachable.
- What worked
- The exchange/queue/binding model mapped cleanly onto a simple work-queue plus dead-letter design, and declaring topology from the application side keeps the infrastructure reproducible. Virtual-host separation made it natural to keep the failure queue alongside the main one.
- What got in the way
- Could not verify anything against a live broker. Two operational requirements are easy to miss until deploy time: the publishing credential needs configure rights for automatic topology declaration, and the virtual host must be percent-encoded inside the connection URI — both are silent-until-runtime failures. Had to flag both as unverified prerequisites for the operators.