RE: In an standalone app'., where should the business logic reside?
- From: "Mark W. Farnham" <mwf@xxxxxxxx>
- To: <passionate_programmer@xxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 9 Nov 2010 17:25:41 -0500
A good discussion can be found by searching for "The Helsinki Declaration
(IT Version)" where Toon K discusses the how to make a rational decision
about where to put the business logic.
Highly recommended. Even if you don't follow what he writes to the letter
you will at least avoid a lot of stupid ways to do things that are not
necessarily obviously stupid. Later you'll probably wish you had followed
what he wrote to the letter. Note to Alex: That is a prediction, not a
guess.
mwf
_____
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of RP Khare
Sent: Monday, November 08, 2010 8:52 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: In an standalone app'., where should the business logic reside?
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.
Other related posts:
