Wednesday, September 19, 2007

Worse than J2EE

There's an interesting thread on the OTN PL/SQL Forum about Real Time Database Design. At least that's how it started. It has now morphed into another pop at J2EE and .NET developers. Zlatko Sirotic has posted a nice satire of the average OO developer's approach to databases:
METHOD 4: sending XML files to OO2EE.Net;
super-fast and clean method that ensures database independence;
we need database independence - maybe one day we must replace our RDBMS with flat files

Which is almost too true to be funny.

I fear my latest contribution to the debate is likely to spoil my chances of getting a Director's tiara to go with my ACE of spades.

It is worth bearing in mind that it is not just OO developers who have a poor understanding of databases. This recent WTF story shows how a VB developer with just the wrong amount of knowledge can inflict a lot worse than J2EE on your system.

2 comments:

Noons said...

:-)

Too funny!

Unknown said...

"we need database independence - maybe one day we must replace our RDBMS with flat files" .. that old crock!

I continue to be surprised how the "database independence is good for the company because we can switch platforms later" still passes muster as conventional, received wisdom.

I've personally never seen anyone reap this particular benefit! Usually by the time a platform migration is considered (if at all) there are many more significant issues at hand.

The cynic in me believes the true rationale is actually a developers' agenda: "database independence is good for programmers because we can easily hop from job to job with our generic database/sql skills"!