Backend Overview
Set baseline backend architecture for maintainability, integrations, and growth.
Recommended approach
- Use NestJS as default backend framework for growing products.
- Keep module boundaries aligned to domain capabilities.
- Prefer explicit API contracts and migration-safe data changes.
Alternatives and when to choose them
- Single fullstack runtime backend for small projects or MVPs.
- Small abstracted backend (Express, Hono, Elysia) for simple APIs or for maximum flexibility
Implementation checklist
- Define domain modules and ownership.
- Define API style (REST + OpenAPI by default).
- Define background jobs, mailing, and payment integration boundaries.
- Version APIs by default, even if starting with v1.