.net - Hosting WCF in IIS 7.5 vs Windows Service for Performance Considerations -

i have simple , direct question: there performance benefits (or other type of benefit) unaware of when comparing hosting of wcf service in iis 7.5 vs. windows service?

i not in dark on topic , have hosted several wcf services in both hosting environments. start new service has heavier use , wanted 're-visit' topic. right leaning twoard windows service.

i have read posts following: iis wcf service hosting vs windows service gives information, bit out of date (yes @ 1.5 years old; still using codename 'dublin technologies').

there no ding against windows services me because quite comfortable setup, deployment, , configuration (including applying ssl cert port hosting wcf service), not big deal me vs. iis.

i thought application recycling in iis downside hosting wcf service, allowing potential small possible breaks in communication. know .asmx iis hosted service (converting wcf) have receives random '401 unauthorized' (i mean random every 5-10,000 calls kind of thing) , marked idiosyncrasies iis , ability keep communication 100% of time without app pool being recycled (possibly causing issue? -> issue not in question here , reference). wonder iis.

so current day's perspective (a lot of msdn comparison charts out of date too, comparing iis 6) on hosting wcf service on windows server 2008 r2 in windows service vs. iis 7.5. thanks!!

with release of appfabric iis, hosting wcf services on iis 7.5 have gotten bit easier , more reliable. appfabric allows configure services start on application pool start , prevent pool recycling normal web application. provides methods allow wcf service log information health , monitor service.

for recent wcf project, i've gone asp.net 4 , appfabric .svc extensions hosting code. (currently, appfabric has issues monitoring services routed - .svc file required)

here couple more useful links wcf , appfabric:

• monitoring wcf services appfabric
• appfabric-enabled wcf data service walkthrough (c#)

another advantage i've seen in iis method allows create pages next monitor, maintain, , configure services. windows service have either edit config files hand or create application handle you. ability host wcf next webforms/mvc applications management huge plus in book. obviously, you'd need make sure it's secured in way prevent others peering in , seeing status/configuring it.