Notifications
The problem
A home equity operation goes through many hands (partner, analysis, legal, payment) and every stage requires documents and checks. Without a single place, operations stalled and nobody knew which stage they were in or what was missing to move on.
One place creates and delivers notices for the four apps: it takes them from the queue, resolves recipients by permission through auth, stores them and pushes them over SSE to the bell. The sentence is built in the front-end in the reader's language.
Decisions and why
- Recipients by permission
- The sender says "whoever holds CONVEYOR_BELT_CONTRACT_VIEW", not a list of ids that goes stale.
- Only type and params in the database
- No sentence stored: the same notice shows in Portuguese or English.
- SSE with a per-user cap
- At most 3 connections per user and app; opening another closes the oldest.
- Invalid message straight to the DLQ
- With no recipient, retrying is pointless.
requestresponse
Pick a scenario above to watch the message travel through the architecture.
What it looks like
Replica of the pipeline board with fictional data (internal system) esteira.evilrabbit.com.br/lines/triage
Triagem
Conferência de dados2
Marina SouzaGMR$ 480 mil 1 d
Paulo HenriqueR$ 1,2 mi hoje
Combate à fraude1
Ricardo AlvesAPR$ 750 mil 4 d
Validação dos documentos2
Carla PradoGMR$ 610 mil 2 6 d
João ReisR$ 295 mil 2 d
Aguardando aprovação0
Nada aqui