Shared libraries
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.
Whatever more than one service uses becomes a library in libs/: the permission catalog, security config, logging, mail and notification publishers, typed clients and test support.
Decisions and why
- A library, not copy and paste
- One PermissionKey; changing a security rule means changing one place.
- One dependency per service
- Each service pulls only what it uses; its pom shows what it depends on.
- Shared test-support
- The same containers and abstract tests in every service.
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