Re: arrrgh Why Java over PL/SQL

klabu wrote:
> arrrgh !
>
> Our backend enviornment:
> 10gR2 <---> TIBCO <---> Java
>
> <rant>
> can someone please explain to me why is the damn bloody Java layer necessary
> ?????
> Am I daft to say PL/SQL can very well handle it ?
>
> and that AQ can replace TIBCO ?
> <rant/>
>
>
> comments please
> --
> 10gR2

Most probably because people with insufficient knowledge of Oracle out-of-the-box functionality tend to make things more complex than they could/should be and reinvent their wheels... Some are afraid of "vendor lock-in" and significant costs associated with migration to a different platform if at some point the current platform is abandoned for any reason. They want to be "platform-independent", which Java seemingly grants them, and they tend to consider the database (any database) just a mere dumpster they throw their data in, sometimes retrieve, process and throw back in using minimum subset of SQL common to all RDBMSes and completely ignoring what else their particular DBMS is capable of, even though good money were paid for it and by not using its capabilities they are throwing away that money. There are surely other reasons as well.

However, not knowing exact requirements of the task at hand it's impossible to say if your current architecture can be replaced/reimplemented with PL/SQL and AQ, maybe with a bit of server-side Java. Actually, if it currently works, and works sufficiently well, I wouldn't strive to replace it with a solution that might be better, but might as well be worse...

Regards,

    Vladimir M. Zakharychev
    N-Networks, makers of Dynamic PSP(tm)     http://www.dynamicpsp.com Received on Sat Dec 16 2006 - 03:52:58 CST