Databases
StackOverflow2013
Postsdbo
POWhere to move the business logic when moving it out of the database
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhere to move the business logic when moving it out of the database
    text
    copied!<p>I have a CRUD-heavy ASP.NET application with all the business logic in Stored Procedures. </p> <p>As an example, there is an UPDATE stored procedure that's ~500 lines long and contains large amounts of conditional logic, referencing multiple tables &amp; UDFs. The proc takes in the field name being updated and the new value, sets a bunch of declared variables, does a bunch of validation and creates a dynamic SQL statement to do the update. Once size fits all. It's big and confusing.</p> <p>I would like to move the business logic over to the .NET side to make it easier to manage/update, test and put under source control.</p> <p>My question is this: where should this business logic go? </p> <p>Say I have a PurchaseOrder object with a property called 'Factory'. If the Factory gets changed, I need to make sure the new factory assigned makes the product that's on the PurchaseOrder, that it has pricing, and that there is a minimum quantity requested based upon that factory, etc. All these validations require inquiries in the database.</p> <p>Should I have the PurchaseOrder object's Factory setter be responsible for doing the data validation via an 'isFactoryValid' method/property that makes the multiple calls to a generic data access object then do the update if it is?</p> <p>Or do I create a PurchaseOrder/Database 'proxy' object that's responsible for handling just PurchaseOrder-related data access. In this case, would I have an 'isFactoryValid' method in the proxy that's called by the PurchaseOrder's setter and then a call to the proxy's update method?</p> <p>How do I determine if I need to worry about increasing traffic to the database with all these extra calls? </p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload