Design Choice: WCF or Service Stack?

Question

I have three main applications that have their own business functions (networks, active directory and help desk). Each of them runs ASP.NET v2 or v3 and has its own databases. However, the application functions did not merge a bit, so the models were recreated in each application and the application logic with it. So now it’s hard for me to maintain the code. So here is my question:

• Is porting my models and repositories to WCF the smart choice for this type of architecture?

• Does the stack use services like serialized json calls the best choice? I would suggest that this would be faster than creating a central wcf application.

I am not very familiar with communication between asp.net mvc web applications, so please point me in the right direction.

Answer 1

I would recommend developing a service level for the design pattern described by Fowler . This service layer encapsulates various domain models and repositories and handles interactions between different domains / models. It will be an assembly, not WCF or some other kind of web service. If you need a WCF web service, then it will be a very thin layer that basically has a contract that mimics the level of service, and the only goal is to provide a web service interface or API.

, MVC . , . , -, , , . , MVC.

/ AJAX . MVC REST API , POST AJAX, - JQuery, - -.

, . , , REST - AJAX .