How I Structure a MERN App So It Doesn't Rot

The problem with most MERN starters

Everything lives in one server.js for a week. Then routes multiply, models drift, and auth logic ends up copy-pasted in six places. Here is the shape I use instead:

server/
  config/      env, db connection, constants
  models/      Mongoose schemas only, no logic
  routes/      thin HTTP layer: validate, call service, respond
  services/    business logic lives here and only here
  middleware/  auth, errors, rate limits
  utils/       small pure helpers

Three rules that do the heavy lifting

1. Routes never touch the database directly. They call services.
2. One model, one file. No 900-line schema dumps.
3. Auth is middleware, not inline checks. If you see if (!req.user) inside a route, move it out.

Why this scales

Smell	Fix
Route file over 100 lines	Extract a service
Same query twice	Share it via the service layer
Auth checks inline	Middleware

Boring structure beats clever structure. Future you is already grateful.