Re: No future for DB2

From: Noons <wizofoz2k_at_yahoo.com.au>
Date: 29 Jul 2005 00:15:45 -0700
Message-ID: <1122621345.339252.40350@z14g2000cwz.googlegroups.com>

Serge Rielau wrote:

> IMHO in the early days of IT (when I was playing in the dirt...) the
> database ruled and the apps were made to fit. Nowadays the trend is that
> the app rules and the DBMS is made to fit.
> T'is what I see anyways...

Sure. But there is still a very clear limit: going back to the volumes bit I mentioned above. Those of us who still have to process serious amounts of data in as little time as possible are still using good old C/C++, shell scripts, perl here and there and maybe in a moment of light-headed enthusiasm, python/php. (Now, THOSE are interesting languages!)

Because very clearly Java, J2EE and XML technologies haven't got a SINGLE chance in heck of ever coping with serious volumes and STILL remain cost-effective. And that has been made painfully clear to me beyond any doubt: nowadays that I have to cope again with seriously large data volumes instead of the total JOKE of Java "apps" I've had to deal with for the last 4 years.

(before the usual band of demented CRETINS jumps in with the "internet shopping carts" and the "12-table schemas": I don't give a CRACK about any of that! I'm talking about serious volumes of data processing, with SENSIBLY priced hardware. Get lost. Not interested. You're a waste of time and space. Capice?)

Agree with you: IMS, RDBMS and XQuery will all find the appropriate niches. But when it comes to speed, IMS will reign supreme. When it comes to volume, RDBMS will eat everything else for breakfast.

And somewhere in between the cracks will be the shopping carts sending their schema meta-data all over the place with a little bit of data interspersed here and there.

Of course: time will tell. Well, at least I intend to be listening! ;) Received on Fri Jul 29 2005 - 02:15:45 CDT