Re: In an standalone app'., where should the business logic reside?
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: passionate_programmer@xxxxxxxxxxx
- Date: Wed, 10 Nov 2010 07:54:49 +0000
I've never met a standalone application. Not once. There are
*always*requirements for other systems to interface with it, users to
get data via
ODBC etc. If they don't exist at go-live they do exist by year 2. Its often
the fact that these things come along and the business logic is only in the
front end that *causes* the sorts of probelms described by Andrew. Data gets
directly loaded or edited without being validated by the business logic and
turns out - despite the protestations of the users - to be invalid.
On Mon, Nov 8, 2010 at 1:51 PM, RP Khare <passionate_programmer@xxxxxxxxxxx>
wrote:
Hi,
I read Tom Kyte's "Effective Oracle by Design". There he says to write most
of the code in the DB itself to reduce application code. It is good in a
distributed environment, but is it advantageous in an standalone application
also?
My app. is in .NET.
................
Rohit.
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
Other related posts:
