Re: choices regarding where to place code - in the database or middletier
Date: Mon, 26 Jan 2004 08:42:48 -0800
Daniel Morgan wrote:
>> Sure! *I* tend to council against complete DBMS independence. This is not >> for love or preference for a given DBMS product, but in acknowledgement >> that a significant portion of the DBMSes capabilities are presented in a >> proprietary way.
> What you are counselling is that people write some of the worst possible
> code and NOT take advantage of those features and capabilities that make
> a product worth the money.
Odd, and wrong. see below.
> And just because at some point years later they MIGHT decide to change
> to another product where they can once again write mediocre code with
> minimal performance and scalability.
> On one hand you toot BEA's horn by saying the Oracle gets its best
> performance with BEA. Then you advise removing the beast's teeth and claws.
> Sounds a bit schizophrenic to me. Buy my product because it makes Oracle
> blazingly fast ... but when you implement it ... don't take advantage of
> any of those features that make it blazingly fast.
[Quoted] I'll try to make it clearer for you. An example of what DBMSs do well, but proprietarily, are stored procedures. I say "use them, to the extent, and in the way a DBMS implements them, rather than try a lowest-common-denominator SQL92-from-client model".
[Quoted] [Quoted] As to what the DBMS does not do well, and which BEA (or any other excellent middleware manufacturer) does do well, I need say nothing. Ask Oracle's best core performance engineers why they use BEA in their top TPC-C benchmark.
There is no dicotomy in a system that contains middleware doing what it does best and a DBMS doing what it does best, even if in a proprietary way.
Let me know if you have any more questions, Joe Weinstein at BEA Received on Mon Jan 26 2004 - 17:42:48 CET