JD.
JD.

Reputation: 15531

Moving webservices to point to on virtual directory

Currently we have 5 web services each one configured in IIS with their own virtual directory.

We have now moved all the webservices into the same virtual directory folder.

Will this have any impact on performance or any other problems?

JD.

Upvotes: 0

Views: 156

Answers (2)

Mehmet Aras
Mehmet Aras

Reputation: 5374

Just a couple of things to keep in mind.

  • By consolidating your previously separate web services into a single virtual directory, you now have a single web application. That means that you're losing your ability to configure each web service separately. All five web services will use the same request queue for the application pool that your web application is assigned to. If several of your web services are getting high traffic, it may cause the requests coming to the other ones to queue. Note that this would still be the case if you had your web services separate but assigned to the same application pool. However, then you would have had the option and flexibility of creating a new application pool and assigning your web services appropriately. Also, each application pool has a recycle setting. It may recycle after so many requests. So if you have one or more high traffic web services, they may cause the worker process recycle and affect the other low traffic but critical web services for example. If you have some data cached for critical web services, you would lose them.
  • You can't take down some of the web services and leave the others ones running. You may want to take one or two offline while still keeping the others running. Previously, you could have shutdown their application pools but now you can't do that because that would mean the other web services that you want to keep running will also be shutdown. You can rename the corresponding asmx or svc files to take some services offline but that just does not sound right.
  • You may want to configure the application pools for some of the web services differently for recycling, performance, health, and identity. However, now that they're all part of the same web application, you can't.

These may or may not be important or critical in your case. Nonetheless, I want to mention so that you take them into consideration if you have not already done so.

Upvotes: 1

John Saunders
John Saunders

Reputation: 161773

No, there should be no impact on performance, or other problems.

Upvotes: 0

Related Questions