Mesfecho

Spring on Lambda

mesfecho.com
The problem

Knowing before the month ends whether the family budget closes, with no spreadsheet, on everyone's phone, and with a low, predictable cloud bill.

Java on Lambda is usually dismissed because of cold starts. With SnapStart, Spring boots once at publish time, AWS keeps the snapshot and every start restores ready memory: 1.3 s on the first measured call. Versions switch through the live alias, with no downtime.

Decisions and why

SnapStart instead of switching languages
I kept Java, Spring and JPA with the same rules as conveyor, and removed the startup cost.
arm64
Graviton is cheaper per millisecond and Java runs the same.
The live alias moves only once the version is up
If the new version fails to start, the previous one keeps serving. Nobody notices a bad deploy.
Liquibase at startup, additive migrations
The previous version keeps working with the new schema during the switch.
Secrets from SSM at startup
No secrets in the package. Catch: they end up in the snapshot, so rotating a secret means publishing a new version.
requestresponse
Pick a scenario above to watch the message travel through the architecture.

What it looks like

Replica of the real dashboard with fictional data
mesfecho.com/dashboard
Dashboard Novembro de 2026
Transações do mêsR$2,708.80
PagoR$2,199.00
A pagarR$509.80
81% Pagas x pendentesMarque contas como pagas em Transações e veja o gráfico mudar.