All geek questions in one place

WCF: Service Hosting Beyond IIS Makes IIS Atrophy

It looks like MS is kicking in the foot by allowing WCF services to be hosted outside of IIS. IIS is a relatively simple yet redundant layer for services from my point of view. Implementing WCF greatly simplifies maintenance, making IIS atrophy. So what do you think? Am I missing something? Why should I use IIS for WCF? Because I see no reason.

+3
source share
3 answers

Hosting inside IIS has its advantages if you want, that is. Use the asp.net core infrastructure for authentication and authorization. Remember that this requires that the attribute AspNetCompatibilityRequirementsModebe set to Required. It also gives you access to HttpContext.Current for easily retrieving post-values, cookies, etc.

http://msdn.microsoft.com/en-us/library/ms734710.aspx

  • WCF services hosted in IIS are deployed and managed like any other IIS application, including ASP.NET and ASMX applications.
  • IIS provides process activation, health management, and recycling capabilities to increase the reliability of hosted applications. Access to Health Monitoring features allows you to monitor the status of your web application.
  • ASP.NET, WCF, ASP.NET, ASP.NET, .
  • WCF, IIS, , ASP.NET 2.0, .
+6

. , (+1 ), IIS WCF:

+3

, IIS 7/7.5, Windows Server 2008/2008R2. , IIS 6 IIS (, net.tcp). IIS , , , .., . SSL , . IP- .. URL- , .svc, WCF 4.0. , IIS, web.config . , IIS . Appfabric IIS extensions you get very detailed monitoring and a panel of your service calls (for example, calls / sec, failed calls / sec, call duration, etc.).), Constancy of service calls for hosting services, workflow, etc. You can also track all your IIS sites for the whole company from one central console, and I think there is even an appfabric integration with SCOM

In short, I believe that for hosting at the enterprise level, IIS and Appfabric should choose hosting for WCF services.

+1
source

Source: https://habr.com/ru/post/1785133/

More articles:


All Articles