Host my service in IIS or windows service?

I have a couple of services, where one of them needs to be a singleton service. The other services connect to this singleton service and the singleton service in turn makes calls back in to the instance开发者_如何学编程s of the other services.

My question: is it safe to move this scenario into IIS so I can make use of the new Windows Server Appfabric features? I'm not sure how IIS handles instance management.

I would go for IIS as well because compared to other hosting mechanisms you get a lot features for free:

• process life-cycle management,
• process recycling,
• shared hosting,
• on-demand activation,
• health monitoring

IIS should not be problem in your scenario. If it already works with self hosting it should also work in IIS. You only need to be aware of some IIS management settings which control AppPool recycling etc.

Hosting in IIS is the way forward definitely. Especially if you have AppFabric installed as you mentioned.