@figuerres: Let's assume that the same environment and variables exist equally for either scenario with the only variable being whether the web service calls are in few services or if they are split across many more services. However, the planning is in anticipation of ever increasing volumes of client calls to the services.
Maybe IIS would perform more efficiently serving a few services because it has to do less "switching" between allocating resources among the services. I dunno.
Maybe IIS performs well on services up to a certain size service and then its performance curve hits a wall. I dunno.
I liken this to the art of indexing a database table and the rationalization of balancing read performance with insert/update/delete performance.
Maybe having 1,000 web service methods allocated across 1,000 web services is just as efficient as having those same 1,000 methods all in a single web service. I dunno.
What do you think?
