Re: New trend in modern IT consultancy - use your relational database as flat file

pagesflames_at_usa.net (Dusan Bolek) wrote in message news:<1e8276d6.0305120753.54198e31_at_posting.google.com>...

> In fact all relational theory is obsolete, DB architect position is
> obsolete and any other database related stuff is too boring for them.

Don't forget Scott Ambler's "Thou shalt not need a data modeler nor a designer, patterns do everything!".

> Of course there is no referential integrity (foreign keys slow things
> down and we have all needed checks in our application), no triggers
> (do not need them all logic runs on app server). Database model is
> cyborg only readable, but that's no problem any more (you should never
> access database with anything but our fancy DB access layer written in
> JAVA).
You forgot also that joins are useless and only overhead when the data access layer in Java "cache" can do the same using a "pattern"...

> sounds you best). Developing company doesn't have a single DB
> specialist (do not need them, just JAVA coders) and database layer has
> no DB specific parts (our application can run on all database
> platforms with no changes at all).

Ah yes. Real world example:

1- Tune the darn database, it's too darn slow!

We do, it gains us 10 seconds in 1800.

2- At the end of a lot of meetings, we ask them to tune ONE method written by a Java "programmer" that must have been on sniff.

They do, and the runtime drops from 1800 secs to 600.

Bottom line conclusion:
we need database tuners with more knowledge of "our product"...

> What do you think about this? It seems to me that this trend starts to
> be very popular in J2EE world.

"starts to be"?????
It's been there from the VERY start!!!
Sun has made it a mantra of Java that all you need to do is know its product and nothing else.

One of the reasons I reckon .NET is going to overtake all this J2EE bullshit.

Cheers
Nuno Souto
wizofoz2k_at_yahoo.com.au.nospam Received on Mon May 12 2003 - 18:08:35 CDT