Three weeks ago I shared an early version of this project and got a lot of thoughtful feedback.
I've since reworked it - here’s the updated version:
https://github.com/prod-forge/backend
What this project is about
The idea hasn’t changed:
Writing backend code is the easy part.
Everything around it is what makes systems reliable.
This project focuses on:
- what happens before code
- what happens before deploy
- what happens when things break
What’s inside
A simple Todo API, but built like a real production service:
- CI/CD with rollback
- forward-only migrations
- observability (Prometheus + Grafana + Loki)
- structured logging + correlation IDs
- Terraform infrastructure (AWS)
- E2E testing with Testcontainers
What changed after feedback
- improved structure and documentation
- clarified migration and release flow
- refined CI/CD and rollback approach
- better explanations of key decisions
Important
This is not a boilerplate.
The goal is not to copy configs,
but to understand how production systems are actually put together.
Feedback
If you’ve worked on real systems:
What would you add or do differently?
