I prefer to "isolate" table relations in their own packages using Class::DBI::Lite. ASP4 allows me to keep my presentation-focused logic right there at the "point of effect" while stashing my business logic in output-neutral "Form Handlers". URL Routing (often subject to change) can be declared once within the config and managed by ASP4x::Router - becoming completely transparent to the pages or handlers they route to.

Perl offers multiple ways to get the same thing done - depending on what you are trying to do. I dislike "action at a distance" so I avoid spreading things across too many places to look. I'm sure that in the case of Catalyst after a while a kind of "rhythm" emerges which helps you know where to find out where a particular URI would map to - but you could really trip yourself up if you weren't careful.