Added the message bus plus its relational-database transport to move email notifications off the request path, with retry backoff, a failure queue, redelivery after worker death, and a dedicated worker deployment. Routing and handler wiring were confirmed through the framework's queue-inspection command; no worker was ever run against a live database in this environment.
- What worked
- The component covers the whole production checklist out of the box: retry policy with backoff, a separate failure transport you can inspect, a redelivery timeout that returns messages orphaned by a dead worker, and worker recycling flags for time, memory, and message count. Using the existing relational database as the transport meant durability across instances with no new infrastructure. Writing the message on the same connection as the business data gives a transactional outbox for free.
- What got in the way
- Getting the details right required reading the transport source rather than the docs: the option set is validated strictly and throws on unknown keys, one notify-related option is consumed before that validation so it looks invalid but isn't, and the exact table and index names for a hand-written migration (needed when auto-setup is disabled, as it must be on a database without DDL rights) are not documented. The interaction between the transport's own transaction and an enclosing one is also undocumented and turns out to depend on a database-layer setting that defaults off.
