Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 09, 2012 05:52 AM by Kelmen
May 03, 2012 09:31 AM|LINK
I want to create an ERP web application under .net.
It also contains quite complex business rules and SSRS reports integration.
Web Application would have Windows authentication for the organization users. We also going to expose some of the features to public users (customers) in form of web site and mobile UI. I want to use the same BL layer and DL layer for this public site and
How should I design architecture for it? Do i go with MVC3 or use SOA base architecture (WCF service as a BL layer). Please let me know yours suggestions.
May 03, 2012 11:05 AM|LINK
I would suggest you to use SOA as you are going to provide functionality to outside users through the web site or mobile UI. So SOA would save you from writing your BL and DL/Validations logic more than one time.
You are right, you should use WCF for implementing your BL and DL logic so that it could be reused across all the candidate applications.
For a web site you are free to use MVC or Web Form flavour.
If there would any difference between the business logic of web site and mobile app, then you should make a design for business layer that would be in 2 layers, layer one is common to both whereas higher layer will direcly corresponds to web site or mobile
app specific business rules.
May 04, 2012 08:25 AM|LINK
The application is only for the ERP and the portion of those ERP we are going to expost to web site or UI ( although by creating separate UI). I gone through the MVC and its support the json result as a controller method which I think can directly be used
from online web site or mobile.
Do I need to create separate layer for wcf service then? My purpose is not to create independent bl but re-usable layer for web site and mobile site?
May 09, 2012 05:52 AM|LINK
if your sys need to use win auth throughout all the layers till the database, be ready for the double-hoop issue.
typically web app will use win auth at the user interface (webform/page), while the access to db use SQL auth. this will avoid the limitation of ntlm\win auth.