Re: "We don't do triggers"

From: Frank <fbortel_at_nescape.net>
Date: Fri, 28 Nov 2003 10:48:58 +0100
Message-ID: <bq756d$n0$1@news4.tilbu1.nb.home.nl>

Daniel Morgan wrote:

> Frank wrote:
>

>> Volker Hetzer wrote:
>>
>>> "Frank" <fbortel_at_nescape.net> schrieb im Newsbeitrag 
>>> news:bq34ho$qr$1_at_news4.tilbu1.nb.home.nl...
>>>
>>>> What if you have customers that wish your product to run
>>>> on a variaty of backends?
>>>> Makes sense to put (1 version!) of the business rules in
>>>> the middle tier to me. Use the database just as a pool of data;
>>>> no logic
>>>
>>>
>>>
>>> What if they wish to use a variety of middle tiers?
>>>
>>> Greetings!
>>> Volker
>>
>>
>>
>> I tell 'm I don't do that ;-)
>> Seriously - the customer can have any middle tier as long as
>> it's black - sorry, Java.
>>
>> The background of all this is simply a matter of
>> development cost - it's cheaper (at least, thought to
>> be!) to develop the logic in one flavour (Java), than in,
>> say two or three (Oracle: PL/SQL, SQL Server: TSQL, DB2/MySQL/...)

>
>
> Surely you can'be believe forcing one middle-tier solution is cheaper
> than forcing one back-end solution. All you've done is shift the restraint.
>
> Put all logic in the database and you can connect from any middle tier
> and any front-end.
>
> Put the logic in the middle tier and you can't connect from any
> front-end that doesn't go through that specific middle tier or the
> entire solution dies painfully.
>
> To you that is better?

Daniel,

given the fact that:
- this is a web based solution
- SQL Server as well as Oracle backends *need* to be served

Would you allow two development teams, or three?

And how many middle tiers -other than supporting Java- can you think of?

-- 
Regards, Frank van Bortel

Received on Fri Nov 28 2003 - 03:48:58 CST