Question

So I have an application I am working on at work that we have a few hundred clients running on. We are working on a brand spanking new ASP.NET MVC 3 app for it, and I am working on the routes for this app.

I posted recently on a solution I came up with for dynamic routes, and it works fine on a few entries I have in a Sql Express DB. Essentiall it creates routes for every entry that I have in this DB.

So, my question is…If I were to implement this on an enterprise application, would the creation of several hundred if not thousands of routes added into my application have any negative consequences?

Answer 1

Concerning the dynamic route table, there is a recommendation which you seem to follow already:

Use named routes. Named routes are an
optional feature of routing. The names
only apply to URL generation – they
are never used for matching incoming
URLs. When you specify a name when
generating a URL we will only try to
match that one route. This means that
even if the named route you specified
is the 100th route in the route table
we’ll jump straight to it and try to
match.

Besides the number of customers / routes, you should also consider the estimated number of requests per day (for which you should be worried more, IMHO), and take into account the scalability of your web server (worker threads, hardware, …) in consequence.