01
- Rescue
- A memory alarm pausing publishers, a backlog that will not drain, or a cluster node that will not rejoin. We stabilise the broker first and explain what caused it after.
02
- Queue design
- Classic, quorum or stream chosen deliberately per use case, with policies and arguments that match the durability and throughput you actually need.
03
- Consumer reliability
- Prefetch, concurrency, acknowledgement semantics and dead-letter paths reviewed against real workload, so a single bad message does not take an entire consumer fleet down.
04
- Migration from mirrored queues
- Moving deprecated mirrored classic queues onto quorum queues or streams with a plan for cutover, idempotency and rollback.
05
- Upgrades and clustering
- Minor-version upgrades rehearsed on a copy, Erlang version alignment, cluster partitions and the Mnesia bits that production teams usually hit the hard way.
06
- Managed Tech
- Backlog alerting, resource watermark tuning, policy reviews, upgrade planning, and an engineer on call when the broker throttles during a traffic spike.