Backend
Ledger — opinionated HTTP core
Service boundaries, validation, and observability hooks for APIs that move money, data, or state — without a hundred micro-packages.
Backend-focused; runtime and package layout are defined in the shipped README.
Overview
Ledger prioritises predictable request lifecycles: clear error envelopes, idempotency-friendly handlers, and job hand-off points you can wire to a queue when you need scale.
It is built for teams who outgrow throwaway routes but refuse a framework soup nobody can grep.
Highlights
- Handler map that keeps transport details from domain rules
- Structured logging and request correlation stubs
- Rate-limit extension point at the edge adapter
- Migration-friendly config split for twelve-factor deploys
What you get
- OpenAPI-friendly route organisation — generate when you are ready
- Contract tests layout for critical paths
- Dockerfile and compose stubs for parity across machines
- README runbooks for secrets and rotation