I like avoiding stored procedures because they tie you tightly to the specific database, create deployment complications, and PL/SQL is far from my favorite language.
Stored procedures are a great way to separate the logical model (which is how the programs look at the data) and the physical model (which is how the data is laid out in tables). Stored procedures greatly increase the flexibility of your solution; they make scaling much easier; they allow you to much easier enhance your code.
I used to work for a company that wrote a large financial software package. Millions of lines of code, close to a thousand binaries, and about 1500 tables. Parts of code touched the tables directly, better designed parts used stored procedures to access the data. Guess which parts were a nightmare to modify?
Abigail
In reply to Re: N-tier, client/model, and business rules?
by Abigail-II
in thread N-tier, model/view, and business rules?
by LameNerd
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |