Geek Answers Handbook

AppFabric for WCF Services on Windows Server 2008 R2

We are currently on a Windows 2008 R2 server, IIS 7.5, and we are going to open some of our data through WCF services.

To do this, we plan to host our services in IIS, but I heard that this is not very good for WCF services.

The problem with WAS is that it is shared hosting. he actually doesn’t realize that he actually has a WCF service or a website (as far as I know)

I heard that we can install the extension on WAS called the Windows Server AppFabric.

  • Does anyone have any experience with AppFabric?
  • Should my application use the so-called Service Bus to use AppFabric?
  • Should I go ahead and definitely install it?
  • at the most basic level, how and where can I install it? Does it require any license?

Thanks in advance.

+4
source share
2 answers

I don’t think IIS has a bad idea - many developers use IIS to host their WCF services. IMHO you would use only what you need, so if you need a hosting infrastructure, IIS is a very good option for WCF services. He (almost) does not know that he is hosting the WCF service, but in most cases this is not a problem.

Windows Server AppFabric, since it is currently released, provides three options: a distributed caching system (so if you need to scale your service, you can use this cache to share state between nodes); packaging / deployment interface (in which you can package a project and simplify it a bit in IIS); and a management / monitoring interface (where you can control the instances of WCF and Workflow services that are running on your computer).

Answers to your questions:

  • Yes, some people have experience :)
  • No, the application should not use it. You should use only ServiceBus if you need its functionality (relay)
  • Only if you need it. For example, if you do not need caching or monitoring capabilities, I would say that you do not need it. In the past, I found that the fewer components that I have in my system, the less likely it is to break.
  • Go to http://msdn.microsoft.com/en-us/windowsserver/ee695849.aspx . AFAIK, you don’t need a license, but you can check on the download page to see if it has more information.
+3
source

There is no real common reason why not host the service in IIS / WAS.

If you want absolutely, completely 100%, make sure that your service constantly starts some process, such as a continuous cycle or a polling monitor, and if any interruption, no matter how brief, is a serious problem, then you will want to search for alternative hosts.

Win Server AppFabric is most useful for hosting and caching WF services. Please note, however, that Win Server AppFabric + Win Server Service Bus 1.0 represents the first steps in convergence between the Azure platform and the private Windows Server platform ... In other words, whichever of the two methods you choose, what will be making bread and oil after 5 years.

0
source

More articles:


All Articles