I'm looking for advice/best-practices/+ve/-ve or other idea's on deployment and maintenance of many (50) Web Services and Web Service Applications on IIS across an application server cluster of 10 machines for Service Orientated Client (WinApp) Software.
Currently we have one solution that contains many Web Service Projects. Software is developed separately and later integrated when ready for release. This involves the integration manager (unfamiliar with the code), adding the project to the main solution and ensuring everything works, e.g. references etc. aren't broken. This means we end up with one site in IIS that serves many web services.
An recent alternative idea, is to have multiple sites - possibly grouping related web services into one site, but keeping other web services in different sites, although this increases maintenance (as there are more sites) it means parts of the software can be updated separably and tested, by the dev who wrote the code.
May be relevant: We use source control for the code, have many users (around 1million hits a day) and can tolerate 0 downtime during working hours.
Currently to update a single web service, the application server must be taken out of the cluster, updated, then added back into the cluster.
Is there a more efficient/flexible, yet still maintainable way of going about this?