Express Router Best Practices for Large Apps

Express Router Best Practices for Large Apps

As your Express app grows, putting every route in app.js becomes a mess. Here are router best practices for large apps.

1. One Router Per Feature

Create a router per feature: routes/auth.js, routes/users.js, routes/feed.js, routes/chat.js, routes/payments.js. Each file owns its routes.

2. Mount Under a Path

app.use('/auth', require('./routes/auth'));
app.use('/users', require('./routes/users'));
app.use('/feed', require('./routes/feed'));
app.use('/chat', require('./routes/chat'));
app.use('/payments', require('./routes/payments'));

The router's paths are relative to the mount path. Clean and discoverable.

3. Version Your API

app.use('/api/v1/auth', require('./routes/v1/auth'));
app.use('/api/v1/users', require('./routes/v1/users'));

When you make breaking changes, add v2. Old clients keep using v1.

4. Apply Per-Router Middlewares

// routes/admin.js
router.use(auth);
router.use(requireRole('admin'));
router.get('/stats', getStats);

Every route in admin.js requires auth and admin. No need to repeat per route.

5. Keep Public Routes Outside Auth Routers

// routes/auth.js
router.post('/signup', signup);          // public
router.post('/login', login);             // public
router.use(auth);                          // everything below requires auth
router.post('/logout', logout);
router.get('/me', getMe);
router.patch('/me', updateMe);

6. Use a Service Layer

Routes bind to controllers; controllers call services. Keep logic out of routes.

// routes/users.js
const { listUsers, createUser, getUser } = require('../controllers/userController');
router.get('/', listUsers);
router.post('/', createUser);
router.get('/:id', getUser);

7. Use Validation Middleware Per Route

router.post('/', validate(createUserSchema), createUser);
router.patch('/:id', validate(updateUserSchema), updateUser);

8. Use Async Handlers

Wrap async controllers with asyncHandler so rejections go to the error handler:

const asyncHandler = fn => (req, res, next) => Promise.resolve(fn(req, res, next)).catch(next);
router.get('/', asyncHandler(listUsers));

9. Nested Routers for Nested Resources

// routes/users.js
const postsRouter = require('./posts');
router.use('/:userId/posts', postsRouter);

Now /users/:userId/posts/... hits postsRouter. Limit nesting to one level.

10. Keep app.js Thin

app.js should only: create the app, apply global middlewares (json, cors, helmet), mount routers, register the error handler. Everything else lives in feature folders.

The Takeaway

For large Express apps: one router per feature, mount under a path, version your API, apply per-router middlewares, keep public routes outside auth routers, use a service layer, validate per route, use async handlers, nest routers for nested resources, and keep app.js thin.