Last post Jun 05, 2012 11:33 PM by bklooste
Jun 05, 2012 01:00 AM|nirman.doshi|LINK
I am in process of identifying best possible architecture for my MVC application before I start actual development.
I have almost figured out other things, but one confusion is still there.
I will have one WCF service, and MVC application will interact with this service.
WCF service will make callls to Business Logic (DLL), which internally will make calls to Data access layer (DAL). I am not sure if there is a need of additional layer in name of Business Logic, or do we generally place Business logic code within WCF service?
Could anyone please suggest what should be the best practice here?
Jun 05, 2012 01:14 AM|amitpatel.it|LINK
I have also the same kind of senario so I have introduce one bussiness logic with service classes. that will be a separate entity and loose couple from mvc application so that can be used by mvc application ui (view + controller) or any of the wcf or window
Below are the details for this.
Jun 05, 2012 11:33 PM|bklooste|LINK
Yes WCF or Ria Services are good places for business logic. I normally go with somethign like this
# people on project
1 Blend data/ business try to keep ui seperate. Get it out there than redesign if needed , the cost for fixes is not that high.
3 Seperate UI and business , data should be seperate but dont try too hard,
10+ Seperate View , View model , BL and data . Consider command queing and UI modules for larger projects. Favour XML over Json unless the application has no external interfaces.