Overview
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.
Home equity contract platform. Four front-ends for four audiences (platform operator, partner managing itself, partner operations and the internal pipeline), seven independent Java services, one PostgreSQL with a schema per service, RabbitMQ for consequences, all in one monorepo.
Decisions and why
- Monorepo, independent projects
- Everything versioned together and reviewed in one PR, yet each service has its own pom and starts alone. No parent POM: what is shared is a library.
- One front-end per audience
- Who administers whom draws the line: switchboard runs the platform, home-ally the partner, hopper its operations, the conveyor the internal flow.
- One-click local stack
- docker-compose with Postgres, Liquibase, RabbitMQ, Mailpit and Loki; data survives in volumes.
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