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.
A personal and group bills app, in the browser and on Android, for the family. One Spring Boot on Lambda, a statically exported Next.js site on S3 + CloudFront, Cloudflare for DNS and bot protection, Neon as the database, and a R$ 100 monthly cap that drove every choice.
Decisions and why
- Serverless because of cost
- Lambda and Neon charge per use: a family does not pay for a server running all day.
- A single service
- No RabbitMQ, no microservices: the domain is small and so is the budget. Architecture sized to the problem.
- The back end is the source of truth
- The API identifies the person only by the JWT sub (RS256) and checks group and role in the database on every read, including before signing a receipt URL.
- Optimistic UI with undo
- On the phone the answer feels instant; if the API fails, the screen reverts and warns.
- Money in cents
- BIGINT, never floating point: 0.1 + 0.2 does not become 0.30000000000000004.
- Limits at the door
- API Gateway at 10 req/s and Turnstile on sign-up: a bot cannot turn the cost cap into a bill.
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.