Route Grouping and Versioning — Node.js & Express Backend

As an Express application grows beyond a handful of endpoints, two architectural concerns emerge simultaneously: how to organise related routes into coherent groups so that each file has a clear, bounded responsibility, and how to evolve the API over time without breaking existing clients. Route grouping and versioning are the answers to these two concerns respectively, and they are deeply intertwined because the mechanism you use for grouping routes also determines how you implement versioning. An unversioned, ungrouped API is a technical debt time bomb: the day you need to change a response shape or rename a field, you face a choice between breaking existing integrations or freezing the API forever. This lesson covers the patterns and trade-offs involved in both concerns so that you can make deliberate choices rather than painting yourself into a corner.

Analogy🏏Cricket

🏏 Think of it like cricket: In a Test match, there are multiple types of scheduled breaks and interruptions, each with different priority levels and timing rules. The lunch break (setTimeout) is scheduled for a specific time but can be delayed if a wicket falls just before — it fires at the next available opportunity after its scheduled time, not at the exact scheduled time. The drinks break (setImmediate) is taken at the end of the current over, as soon as the ongoing delivery sequence finishes. The umpire's over-rate check (process.nextTick) happens immediately after each delivery, before the next batsman faces — it cannot be deferred. The DRS review resolution (Promise microtask) happens between deliveries, after the umpire check but before any scheduled breaks. Just as the match referee would be furious if an umpire kept conducting over-rate checks after every single ball indefinitely (starving nextTick), the event loop is unable to proceed if process.nextTick callbacks keep registering new nextTick callbacks recursively. The insight is that each timer primitive is not just a delay mechanism — it is a specific position in a formal protocol, and misusing it violates that protocol's invariants.