Tech Stack Overview
Compare supported stack profiles and choose the right one for delivery speed and long-term maintenance.
Recommended approach
Default to React Router (Framework Mode) + NestJS for most product work.
Comparison matrix
| Profile | Frontend | Backend | Best for | Main tradeoff |
|---|---|---|---|---|
| Small and quick project | React Router (Framework Mode) (default) or Next.js | Same app runtime | MVPs, pilots, short deadlines | Harder separation as complexity grows |
| Regular product stack | React Router (SPA/SSR) | NestJS (default) | Growing products with clear API boundaries | More moving parts than one fullstack app |
| Enterprise / big project | React Router (SPA/SSR) | NestJS | Large teams, governance, high integration count | Higher upfront architecture cost |
Migration paths
- Small fullstack app -> split dedicated backend when domain/API boundaries become heavy.
- SPA-only frontend -> hybrid/SSR for SEO and faster first contentful render on public pages.
Implementation checklist
- Capture stack profile in an ADR.
- Validate team skills and hiring risk.
- Define scale signals that trigger migration.
- Re-check stack every quarter.
Common pitfalls
- Treating current team preference as universal default.
- Migrating too late after domain complexity is already high.