Could you elaborate in a bit on this? This is the first time I have heard of this, and I find it very interesting.

Ok you add a new route but how do you reference what code should be executed when that route is hit?

We have something that loads up, via requires, the action (or route) that should be run when a URL is encountered.

Second dmak, would love to understand more. I can following dynamically loading routes but can't follow how that would be implemented end to end. Some things I would be interested in: - Where do the keep the code that gets executed for new routes? Is that deployed dynamically as well? - If you are changing routes dynamically how do you test in non-prod, are you constantly syncing non prod with prod? - How do you control what you deploy dynamically vs what you migrate through the environments?