On Friday, March 1, 2002, at 11:38 AM, Dave Rolsky wrote:
> On Fri, 1 Mar 2002, Perrin Harkins wrote: > >> However, there is a big advantage in being able to put most of the >> processing work onto middle-tier machines that are easy to load >> balance. >> Scaling a big Oracle server is expensive, and pretty hard after a >> certain point. Scaling application servers can be as simple as >> ordering >> another 10 Intel boxes. This is one of my main objections to running >> stored procs. > > I used to work at a place (Digital River) that had (and I think > still has) > a giant web app that served up thousands of web stores. > > The entire app was written in PL/SQL and was served with Oracle > 7.x on a > big old Sun 6k machine. They had something like 16 processors > and several > gigs of RAM. > 1 - This is just how the group I worked with at Oracle had things set up. And they too had memory problems. 2 - Why can't you just get several database servers and load the stored procedures into all of them? 3 - I created a CPAN module, SQL::Catalog, which provides some of the benefits of stored procedures (separation of SQL and Perl, centralization of all SQL, access to SQL via file or memory cache or straight from DB) and actually provides more than stored procs in some ways because you can have each query parsed and the statistics on the query stored so you can generate reports on the types of queries you have in the system.
