Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In our application we have very large data.
We would require to do aggregations and calculations for various conditions(based on what user select in UI).
1)Since the data is very large is it advised to do all the
aggregations(business logic) in database(procedures) ?or
2)Will there be a major impact if done in Business Layer after getting data from DB?
As all the data will be converted to objects and then aggregation is done.
I’m assuming your app/web server and your database server are separated. You will want to minimize the amount of data that needs to cross the wire. Besides, data aggregation is something database engines are very good at so you should let them do what they do well. So I’d suggest you do the aggregation in your database.