We are developing a new middle tier for our application package. We strive to rewrite our business logic and data access levels in C # since they are currently located in VB6 and published via COM +.
We are trying to decide how to make this average level available to different customers. We will use WCF for this, and we decided that we will use various bindings to facilitate each client process, including netTcpBinding for our desktop application, net.Tcp and / or named pipe binding for an Internet application that works either locally , or on a machine on the network, and some taste of the HTTP binding for an external web API.
We are trying to decide how to place our service. It seems that most of the places I go say IIS is the way to go, but it looks like you will get the best performance from the BLL / DAL part if it was under Windows Service, and @marc_s here on SO seems to recommend your own most often hosting. So, we host it in IIS under a service or in some kind of hybrid, where, perhaps, a thin service is hosted in IIS for the HTTP endpoint and consumes the main service through net.tcp or named pipe binding? Separating it allows, if necessary, physical separation, as well as the ability to disable IIS, which will still leave the service running for those clients who gain access to the endpoints that it publishes.
Also, what about scalability and reliability? Is there a big difference between the two placement environments?
I understand that there are many questions like this, but I could not find enough information that I was looking for, so links to more specific help work as well as the answer.
source
share