From: "Powell, Mark" <mark.powell2@hp.com>
To: ORACLE-L <oracle-l@freelists.org>
Subject: RE: OT: RE: interview question on schema design
Thread-Topic: OT: RE: interview question on schema design
Date: Wed, 12 Dec 2012 21:35:26 +0000
Message-ID: <1E24812FBE5611419EFAFC488D7CCDD112187092@G5W2734.americas.hpqcorp.net>
References: <DB806F2BEB98ED4FB8172F8CE09447FF946A6CD1E1@EXCH-MBX05.allegisgroup.com>
 <CAJvnOJbR58a0At--qmLDG8YBAOjWHvS3vrbUER3z3HqA0tzVxw@mail.gmail.com>
In-Reply-To: <CAJvnOJbR58a0At--qmLDG8YBAOjWHvS3vrbUER3z3HqA0tzVxw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-To: mark.powell2@hp.com


DBA's in general dislike java applications for just the reason mentioned: bad database access technique.  I am sure there are many well written java applications that access Oracle; it is just that the rule seems to be to code poorly.   Also java programmers have a tendency to try to do what should be done inside the database instance within their code.  I remember reading a forum thread where the java developers were trying to cache the database data within their application where multiple java application servers would be in use since this would be better than having to go to the database for the data!

The problem is not the java language, but rather a combination of  how the java frameworks are designed, inexperienced developers, and poor project management which results in poorly performing applications that kill the database.


-----Original Message-----
From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org] On Behalf Of Andrew Kerber
Sent: Wednesday, December 12, 2012 2:10 PM
To: mbrady@allegisgroup.com
Cc: oracledbaquestions@gmail.com; ORACLE-L
Subject: Re: OT: RE: interview question on schema design

You have expressed exactly why DBA's (in general) are so disdainful of Java programming.  While no doubt there are exceptions, in my experience Java programmers never look at the code underlying their objects, and blame the DBA when their application is slow.**  In particular, Java seems very prone to producing huge numbers of round trips from the application server to the database and back, pulling one row or even one row and one column of data at a time when some very simple query and schema design could get all of the data in a single trip.
On Wed, Dec 12, 2012 at 12:33 PM, Brady, Mark <mbrady@allegisgroup.com>wrote:

> That attitude is promulgated by tools like hibernate (
> http://www.hibernate.org/) which increases the developer's ability to 
> rapidly develop new applications by abstracting the database [away]. 
> It abstracts the database away, so you no longer have to /think/ about it.
> Adoption of those frameworks has been slower in .net communities but 
> where it is adopted you find the same attitude.
>
> <SNIP>
>
>
>


--
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'


--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l