All these routing libraries are just wrong level of abstraction. In HTTP you have resources, and resources are not flat, they are hierarchical. And hierarchy o

All these routing libraries are just wrong level of abstraction. In HTTP you have resources, and resources are not flat, they are hierarchical. And hierarchy of resources defines some connection between then, and some common properties (data, access level etc). So any resource can respond to some HTTP method or can delegate to another, nested resource (if any) for any method. So (in PHP, from our still proprietary framework): // Index resource, just routing, no HTTP method handling. class IndexResource extends Resource { public function __construct(Application $app) { // ... } // Route nested resources for any request public function any(Request $request) { // Static path: $this->path( CollectionResource::Path, new CollectionResource($this) ); } } class CollectionResource extends Resource { const Path = 'items'; // Parent resource type constraint, you can access // parent data using IndexResource API: public function __construct(IndexResource $parent) { //... } // Route nested resources for any HTTP method: public function any(Request $request) { // Regexp pattern for URI segment: $this->match(ItemResource::Pattern, new ItemResource($this)); } // Or handle GET public function GET(Request $request) { // ... } // Or POST maybe public function POST(Request $request) { // ... } } class ItemResource extends Resource { const Pattern = '(\d+)'; public function __construct(CollectionResource $parent) { // ... } public function any(Request $request, $prefix, $id) { $this->item = Item::find($id); } public function GET(Request $request) { return JSON::string($this->item); } } It's not about routers + controllers etc, it's just resources + delegation to nested resources: - recursive routes are trivial, so no problems with CMS-like applications; - looks good with type systems; - no long routing tables (in fact, no routing tables at all), so true modular apps; - you can use anything (e.g. database) for resources lookup, good for CMSes again; - it's absolutely RESTful. Yes, automatic URI building is not so easy, but it's kinda possible, in some semi-automatic way. I wonder why frameworks built this way are so uncommon (ours were inspired by Bullet BTW).