Conveyor

Persistence and migrations

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 Liquibase changelog for everything, run by a container before any service starts. One file per table change, numbered, with a comment and a rollback. Services only validate that the entity matches the table.

Decisions and why

Changelog outside the services
No service migrates on boot: two instances starting together never race over the schema.
An applied migration is never edited
Need a change? A new file. A script fails the local start if anyone edits or deletes one.
CI migrates an empty database and rolls it all back
Every rollback is tested on every PR.
ddl-auto=validate
An entity changed without its migration is a red build, not a production surprise.
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
EsteiraPTGM
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