Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > Java > choices regarding where to place code - in the database or middle tier

Reply
Thread Tools

choices regarding where to place code - in the database or middle tier

 
 
JEDIDIAH
Guest
Posts: n/a
 
      06-24-2004
["Followup-To:" header set to comp.database.oracle.]
On 2004-01-19, Daniel Roy <> wrote:
> Hi Joe,
> I am a Siebel configurator/programmer (Siebel is a "Customer
> Relationship Management" software, which can be considered analogous
> to SAP). My personal experience with the issue which interests you is
> that as much as possible should be stored in the database. Siebel, by
> some twisted reasoning about compatibility of code on various
> databases (it runs on Oracle, SQL Server and DB2), decided to keep


That's just plain silly. Given that all of those products are variants
on a single specification based on SQL, the DDL is the least likely
part of these products to present cross-platform development issues.
Niggling quirks with datatypes (like date/time) are going to be far
more interesting.

My last project involved a product that was ported from msSQL to Oracle
(and then back) with another DB2 port in progress. Outside of stored
procedures, it was pretty simple to use perl to convert an Oracle schema
into something suitable for msSQL.

[deletia]




 
Reply With Quote
 
 
 
 
JEDIDIAH
Guest
Posts: n/a
 
      06-24-2004
["Followup-To:" header set to comp.database.oracle.]
On 2004-01-20, Daniel Morgan <> wrote:
> Joe Weinstein wrote:
>
>> However, that dbms-specific level should be as narrow and
>> controllable/switchable
>> as possible. J2EE standards help there.
>> Joe
>>
>>> Just my 2 cents
>>>
>>> Daniel

>
> I appreciate your opinion and your honesty that your perspective comes
> from selling that middle tier but I completely disagree.
>
> The 'lets push more bytes down the pipe and across all those routers'
> thinking is not going to lead to performance. You may be scalable but
> performance will suffer. And you will be no more scalable than a thinner
> client.
>
> Render under to database everything you can do in the database and let
> the middle tier do what it does best ... fail-over, load levelling, and
> serving up the front-end.


You are painting with far too broad a brush. Some of your examples below
represent absurd examples of middle-tier database processing. They would
(and do) horrify anti-centrists as much as they do you. Some of them
demonstrate that even good ideas can be poorly implemented.

>
> Try tuning all that rotten SQL coming from those fat front-ends sometime
> and you will understand why those here that have experience with
> PeopleSoft, SAP, Baan, and Siebel are remarkably unhappy.
>



--
The public has a right to free music. It's part of the bargain that
was originally made with musicians and publishers. It's time that the |||
debate was shifted to reflect that. Robber Barons and their Toadies / | \
are distracting us from the original facts of the situation.



 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Choices, Choices!!!! Leeland Clay MCAD 2 02-13-2006 01:53 PM
2 tier to 3 tier? NOSPAM ASP .Net 1 10-14-2004 10:51 PM
Choices, choices, choices. Scott Digital Photography 0 10-04-2004 06:15 PM
ASP v2 & 3-tier or 2-tier rob ASP .Net 1 08-13-2004 06:04 AM
Choices, choices stuart.cameron Digital Photography 1 06-28-2004 09:29 AM



Advertisments