WCF 托管选项建议
我正在寻找托管我的 WCF 企业应用程序的建议。
该应用程序。要求运行而不在服务器上停止。它还使用 TCP 在 Intranet 环境中产生最佳性能。
我正在考虑将其托管在窗口服务中，因为 IIS 回收过程，并且超时。
但是，我从 msdn http://msdn.microsoft.com/en 找到了这一点-us/library/ff649818.aspx：
窗口服务...缺乏企业功能。 Windows 服务不具备 IIS 中包含的安全性、可管理性、可伸缩性和管理功能。
是否意味着Window Service不适合企业应用？但是 MS SQL、Oracle、MySQL 等呢？它们都托管在 Win 上。服务好吗？
问候 布莱恩
I am looking for suggestion for hosting my WCF enterprise application.
The app. require to run without stopping at the server. It also use TCP to yield the best performance at the intranet environment.
I am thinking to host it at window service because IIS recycle process, and has timeout.
However, I find this from the msdn http://msdn.microsoft.com/en-us/library/ff649818.aspx :
Window service...Lack of enterprise features. Windows services do not have the security, manageability, scalability, and administrative features that are included in IIS.
Does it mean Window Service is not suitable for enterprise application? But How about MS SQL, Oracle, MySQL etc. They all host at Win. Service right?
Regards
Bryan
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Windows服务适合企业应用！引用的文本实际上意味着 IIS 有很多内置的管理功能，这些功能在自定义托管（如 Windows 服务）中不可用，除非您自己实现它们。
这些功能之一是您想要避免的回收，这有助于应用程序保持低资源消耗（服务器处于健康状态）。另一个这样的功能是 IIS 检查工作线程状态。如果工作进程看起来卡住了（出于任何原因不处理请求），IIS 将自动启动另一个进程并将新请求路由到该进程。
IIS + WAS + AppFabric 可以提供非常大的功能集，但它们并不适合所有场景。如果您的服务需要一些后台连续、计划或多线程处理，那么最好转移到自托管方案。
Windows service is suitable for enterprise application! The quoted text actually means that IIS has a lot of built-in management features which are not available in custom hosting (like windows service) unless you implement them at your own.
One of such features is the recycling you want to avoid which helps application to keep low resource consumption (server is in healthy state). Another such feature is IIS checking of the worker state. If worker process looks stuck (don't process requests for any reason), IIS will start automatically another process and routes new requests to that process.
IIS + WAS + AppFabric can provide very big feature set but they are not good for every scenario. If you have service which requires some background continuous, scheduled or multi threaded processing it is probably better to move to self hosted scenario.