Arch Forum 2025-08-21

Participants: backend devs, Magnus, Andy, Victor, and the web team (Veena and David)

Agenda

• Hydra web dev for backend
• Deadletter reminder

Summary

Hydra web dev for backend

Veena from the web team gave an introduction on how backend devs can make changes in Hydra web by themselves.

Presentation: https://docs.google.com/presentation/d/1m366CybHM0q1Mjk2bwmsreRS23IhkGcibwnE6zGc6sY/edit?usp=sharing

The idea is that for simpler tasks, like adding a button or a column, it is quicker and easier if the backend developer can make the changes themselves. There's no need to have a sync meeting with the web team or wait for them to have time to pick up the task, etc. Exactly what level of complexity can be handled this way depends on the developer; some are more comfortable with web development than others.

(Note: someone from the web team will still always review the change.)

Deadletter reminder

We aim to have 0 deadletters: https://be.minority.com/Best-practices-and-guidelines/Design-Principles/#deadletters

Every day that there are any "deadletters," the developer responsible for that area should investigate and clean them up.
(We should not forget about deadletters in Azure Service Bus; even if there are few, it's easy to miss them now that almost everything is on RabbitMQ.)