Windows服务主机 - 没有IIS - 都柏林在哪里适合？ [英] Windows Service Host - No IIS - Where does Dublin fit?

问题描述

嗨

我们的本地负载均衡应用服务器通过Windows服务托管我们的WCF端点。它是本地网络，.net到.net，tcp +二进制序列化：高吞吐量，高性能方案。

由于不需要IIS，因此甚至没有在应用服务器盒上安装IIS（并且你不需要我需要加强那些不存在的东西，即使有。）
我只看到了一些都柏林的信息，但它似乎是所有的IIS扩展，IIS扩展...
是都柏林是否会提供直接替代在Windows服务下托管的WCF的服务？

干杯新郎

<更新：我忘了提到那些服务器是W2K3 ...

Hi

Our local, load balanced app servers host our WCF endpoints via windows services. It's the local network, .net to .net, tcp + binary serialization: high throughput, high performance scenario.

IIS isn't even installed on the app server boxes since it's not needed (and you don't need to harden what's not there, even with ).

I've only seen a little bit of the Dublin information but it seems to be all IIS extension this, IIS extension that...

Is Dublin going to provide a direct alternative to WCF hosted under a windows service?

Cheers

Ed


Update: I forgot to mention those servers are W2K3...

推荐答案

了解使用Windows服务托管WCF服务的原因会很好。这些服务是否有状态并长期保持应用状态？每台机器有多少这些WCF服务？您是否需要永久保留这些服务（在内存中运行），如果是这样，为什么？

我认为您的答案是 - 我们必须在W2K3服务器上运行，而不能转移到W2k8服务器。是这种情况吗？

都柏林使用IIS管理器扩展来提供管理和监视WCF和WF应用程序的工具故事，与ASP.NET IIS管理器扩展相同。在托管服务时，您不需要IIS，只需安装WAS（Windows进程激活服务）作为WCF服务的进程主机。 WAS使您能够有效地使用计算机上的资源，因为它是基于消息的激活，而不是要求永久可用的Windows服务。都柏林的一个附加功能是它提供WAS托管WCF服务的自动启动，这意味着它启动或"预热"。在收到第一条消息之前提供服务，从而减少第一条消息呼叫的延迟。

如果能够理解WAS是否也适合您的WCF服务以及您的任何限制目前正在运行（OS平台除外）

谢谢。 Mark Fussell
都柏林PM

It would be good to understand your reason for using Windows Services to host your WCF services. Are these services stateful and hold onto application state for long periods of time? How many of these WCF services do you have per machine? Do you need to have these services permanently available (running in memory) and if so why?

I think that your answer will be - we have to run on W2K3 servers and cannot move to W2k8 server. Is this the case?

Dublin uses IIS Manager extensions to provide a tooling story to manage and monitor WCF and WF applications, identical to ASP.NET IIS Manager extensions. When is comes to hosting services you do not need IIS, just WAS (Windows process Activation Service) installed as the process host for your WCF services. WAS enables you to efficiently uses the resources on your machine since it is message based activation, rather than requiring a Windows Service permanently available. An added capability of Dublin is that it provides Autostart of WAS hosted WCF services, meaning that it starts, or "warms up" the services in advance of the first message being received, thereby reducing the latency on first message call.

If would be good to understand whether WAS could also be suitable host for your WCF service and any limitations that you are currently running into (other than OS platform)

Thanks. Mark Fussell
Dublin PM

这篇关于Windows服务主机 - 没有IIS - 都柏林在哪里适合？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！