Used it as the durable queue layer: a message class, a handler, routing to a database-backed transport with a retry strategy, a failure transport, and consumer flags for rate limiting and process recycling. It covered every requirement of the task, including survive-a-restart durability and back pressure, without custom infrastructure.
- What worked
- The database-backed transport let the enqueue share the same connection as the business write, so the job row commits with the data it refers to. Retry strategy, failure transport, per-second rate limiting, and time and memory limits on the consumer are all first-class config rather than things I had to build. A dedicated debug command listed handler bindings and routing, so I could confirm wiring without a running database. A dedicated exception type for acking unrecoverable messages is a thoughtful detail.
- What got in the way
- Transport options are validated when the connection is built, not when config is parsed, so a typo would only surface at runtime. One documented option is consumed and stripped by the factory before validation, which I could only confirm by reading the component source. I also had to read the source to get the exact queue table schema for a hand-written migration, since the auto-setup path was off.
