Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> New trend in modern IT consultancy - use your relational database as flat file

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

From: Dusan Bolek <pagesflames_at_usa.net>
Date: 12 May 2003 08:53:44 -0700
Message-ID: <1e8276d6.0305120753.54198e31@posting.google.com>


Greetings,

for last few years I can see a new trend in consulting companies. In the past they pretended that their people have some database knowledge. However, I think that this is too old fashioned and not enough sexy for them. So they started a new era in consultancy. In fact all relational theory is obsolete, DB architect position is obsolete and any other database related stuff is too boring for them. Up to date consultant should be proud that he has no database knowlegde, best applications have generated data model with tables like this (real world example):

T08000


T08000T002005_0:  NUMBER
T08000T007000_0:  NUMBER
T08000T005000_0:  NUMBER
T08000header___:  VARCHAR2(4000)
T08000footer___:  VARCHAR2(4000)
T08000T008000_0:  NUMBER
T08000attribs__:  NUMBER

T08000methodnam: VARCHAR2(32)

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). This DB access layer maps objects in application to tables and rows within using some unique identifier, it basically means that all range scanning of objects in database needs to be transfered to bunch of single row querries (no problem at all we have great benchmark numbers from SUN/IBM/HP/COMPAQ/MICROSOFT* test labs - * - check what 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).
And on top of it, this approach is usually described as new trend in IT and all previous development not using this madness is called old fashioned or just 70s style.

What do you think about this? It seems to me that this trend starts to be very popular in J2EE world. I think one of the main reasons can be that this gaves a JAVA guy with no database knowledge feeling that he is not ignorant, but very progressive in the world full of relational reactionist.

--
_________________________________________

Dusan Bolek, Ing.
Oracle team leader

Note: pagesflames_at_usa.net has been cancelled due to changes (maybe we
can call it an overture to bankruptcy) on that server. I'm still using
this email to prevent SPAM. Maybe one day I will change it and have a
proper mail even for news, but right now I can be reached by this
email.
Received on Mon May 12 2003 - 10:53:44 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US