Re: choices regarding where to place code - in the database or middletier
From: Daniel Morgan <damorgan_at_x.washington.edu>
Date: Mon, 26 Jan 2004 10:07:32 -0800
Message-ID: <1075140389.219038_at_yasure>
>
>
> Only in a simple one-vendor environment. If you are using more than one
> product,
> both may offer some same bit of functionality, and perhaps you cannot
> use them
> redundantly, but must choose one or other. In this case, the money you paid
> one of the vendors for the feature is already lost. You will presumably
> choose
> to use the one that either works best, or provides some side benefit.
Date: Mon, 26 Jan 2004 10:07:32 -0800
Message-ID: <1075140389.219038_at_yasure>
Joe Weinstein wrote:
> Daniel Morgan wrote:
>
> Hi Daniel. I hope my other response was clear, and this one of yours is
> clearer
> than your first.
>
>> You either fully embrace a software and leverage it for all of its >> scalability, security, and performance features or you are leaving >> money on the table.
>
>
> Only in a simple one-vendor environment. If you are using more than one
> product,
> both may offer some same bit of functionality, and perhaps you cannot
> use them
> redundantly, but must choose one or other. In this case, the money you paid
> one of the vendors for the feature is already lost. You will presumably
> choose
> to use the one that either works best, or provides some side benefit.
As you now explain yourself I agree. Usually those words are used to promote the concept of vanilla SQL rather than bulk binds and other proprietary code that can vastly increases scalability and performance.
-- Daniel Morgan http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp damorgan_at_x.washington.edu (replace 'x' with a 'u' to reply)Received on Mon Jan 26 2004 - 19:07:32 CET