I am developing a distributed architecture where we will have a web interface (possibly ASP.NET MVC and, ultimately, ExtJS), and then a certain number of application modules as backend services, my idea is to completely free them .NET on one or two or three different servers, so I can distribute the workload between several machines.
What technology should I use to write and share data between these basic services?
for example, if I write .NET WCF shells for my business logic (.NET class library), I believe that I can change the binding and use named pipes for high performance in one window or when deploying to multiple servers, which I just change bindings in the configuration file to use netTCP, and everything should work with hope.
About the WCF services themselves, is it better to host them in IIS or in the Windows custom written service?
My goal is to really get the best possible performance and design an architecture that is scalable and reliable, without compromising on network traffic or latency, so I am thinking of WCF and xml web services to use binary translations instead of SOAP.
Thank you, David.
source
share