"JDE uses these APIs to dynamically generate platform-specific SQL statements. Thus, this middleware provides workstation-to-server and server-to-server database access. To accomplish this, both the legacy JDE OneWorld middleware as well as the newer JDE EnterpriseOne middleware incorporate database driver support for a variety of third-party database drivers including ODBC, for connection to Microsoft SQL server, OCI, for connection to Oracle database and Client Access 400 drivers for connectivity to IBM DB2."
As refer to above statement (from wiki), I think it clears lots of doubts that frequently raised by JDE developer: "why can't I just go to the lower level and write my own SQL statement ...?"
Well a lot of us might ask that due to some performance issues that JDE developer frequently faces.
JDE is meant to design in such a way so that it is so generic. However, it is common to the software developer that you have to sacrifice something in exchange for something else.
E.g.: you trade off performance OR h/w requirement for graphics in games.
In this case, JDE decided to trade off some-level of performance for greater database-support-range.
That reminds me a common quote that I often uses: "there is no best software, anything above average is good enough ..." (:P perfectionism might not totally agree with me, but hey ... at least that kills over-budget, behind-schedule or even worst project-dropping).
by Avatar Ng
No comments:
Post a Comment