I'm trying to see which route is best. Having a Business Logic Layer or have all the logic as stored procedures in the database.
The application architecture looks like this: Data Access Layer (LINQ to SQL) -> Business Logic Layer (Needed?) -> UI Layer (Web).
Does it make sense to have the middle layer if everything is done via stored procedures? If not, what do you recommend for the BLL? Could you advice on both routes? Advantages and disadvantages? Kindly note that the application is married to the database (Sql Server 2005) so there is no need to take into concideration that the dbms will change in the future.
sucks! i never ended up using it, but when it was announced i was excited to see a new and refreshing browser. i guess we'll see what Dia has to offer but at first glance, seems like an operator type browser.
maybe tis the end of the browsers as we know it, you know with Opera's Neo and all. exciting times.....i guess......
Question
Bazenga
Hello,
I'm trying to see which route is best. Having a Business Logic Layer or have all the logic as stored procedures in the database.
The application architecture looks like this: Data Access Layer (LINQ to SQL) -> Business Logic Layer (Needed?) -> UI Layer (Web).
Does it make sense to have the middle layer if everything is done via stored procedures? If not, what do you recommend for the BLL? Could you advice on both routes? Advantages and disadvantages? Kindly note that the application is married to the database (Sql Server 2005) so there is no need to take into concideration that the dbms will change in the future.
Thanks.
Link to comment
https://www.neowin.net/forum/topic/868664-aspnet-design-business-logic-layer-or-stored-procedures/Share on other sites
14 answers to this question
Recommended Posts