Arch Forum 2025-05-22¶
Participants: Backend devs, Magnus, Andy & Victor
Agenda¶
- PRs & Renovate
- RabbitMQ Management
- Events Guidelines
Summary¶
PRs & Renovate¶
Demo/refresher of how Renovate works. Details at Renovate
RabbitMQ Management¶
Demo/refresher of how our topology/architecture for RabbitMQ looks. Details at Events And Messages
Deadletters¶
We have a "Zero deadletter vision": https://be.minority.com/Best-practices-and-guidelines/Design-Principles/
Demo of how they can be handled: In RabbitMQ, the deadletters can either be resent (all of them in one go), or discarded (one-by-one or batch-by-batch).
Events Guidelines¶
Discussion around our event guidelines: https://be.minority.com/Best-practices-and-guidelines/Design-Principles/#events
Our guidelines on when to use events vs synchronous HTTP calls are not super clear. In many cases, it depends on the details which way is appropriate.
Extra¶
A question came up about the status of Azure Service Bus and RabbitMQ. As of 2025-05-22, the status is:
- The goal is to migrate everything over to only use RabbitMQ.
- Rate and MF ACH are migrated away from MassTransit, with MF Remittance left to do (this is needed for them to use our RabbitMQ implementation).
- We now have support for normal events and scheduled events.
- Sessions are still unclear. Currently researching how to handle them best since there's no easy built-in way in RabbitMQ.
- One issue with our RabbitMQ implementation is holding it back: If the connection is lost to RabbitMQ, the service will not always automatically reconnect. To heal, the pod needs to be restarted. This must be fixed before more areas migrate.