Skip to content

Choosing templates

A project is usually two to four generated repositories: an API, a front end, and a worker per kind of background work, or an API and its Node worker generated together as one monorepo.

You need Generate
An HTTP API, auth, a database nest-api
A web front end react-app (or react-monorepo, below)
A site its owner edits, or a small shop, with no API of its own next-site, on its own (below)
Slow or heavy jobs outside the API process node-worker
The API and a Node worker sharing one database nest-monorepo (one repository, one Prisma package; why)
Jobs that need Python libraries py-worker
Durable, multi-step workflows --with temporal on the API and a worker (why)
A full stacks project and the services it runs on · Open full screen ↗

react-app and react-monorepo are the same code: react-app is generated from the monorepo’s packages. The choice is about deployment, not code.

react-app react-monorepo
Deployments one image one image per app
Auth screens routes (/login) their own app and origin
Session a plain cookie on one origin one cookie shared across subdomains
Releases together each app independently
Moving parts fewer cookie domain, trusted origins, CORS for every app

Start with react-app. Move to the monorepo when surfaces genuinely need to ship on different schedules, scale separately, or be locked down on their own (an admin console reachable only from a VPN, a marketing site edited daily).

next-site stands alone: Next.js with Payload CMS built in, its own Postgres, its own auth, no API to generate or deploy. It is for the site a business edits itself: company pages, a portfolio, a small shop (--with shop) paid outside the site. Choose the API and front-end templates above instead when the product needs an API of its own: mobile or third-party clients, background jobs, roles and workflows beyond content and orders.

next-site react-app + nest-api
Repositories and deployments one two or more
Content edited by the owner, in Payload’s admin developers, or an admin you build
Data model Payload collections Prisma models behind an API
Payments manual built in, others as adapters yours to build
Link Setting that must match
Front end → API the front end’s VITE_APP_API_URL; the API’s FRONTEND_HOST (and MISC_CORS_ORIGINS)
API ↔ workers (jobs) the same REDIS_*, and the same queue names on both sides
API ↔ workers (data) the same database; the worker’s models match the API’s schema (automatic in nest-monorepo)
API → Temporal → workers the same TEMPORAL_ADDRESS and TEMPORAL_NAMESPACE; the worker polls the task queue the API starts on
Everything → OpenObserve one org per project, a distinct OTEL_SERVICE_NAME per service

Mismatches are mostly silent: a worker on the wrong Redis connects happily and never receives a job. A full-stack project walks through each link.