RE: In an standalone app'., where should the business logic reside?
- From: "Goulet, Richard" <Richard.Goulet@xxxxxxxxxxx>
- To: <passionate_programmer@xxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 8 Nov 2010 09:56:45 -0500
Should a "standalone" app have it;s business login in the database??
Good question, and the answer as in many cases is "it depends". It
depends on what the distance from the database server to the client is,
stored procedures will execute faster inside the database if they need
to access other data. It depends on if there is more than one way to
extract or insert data into the database, stored procedures will make
sure that it's always done the same way no matter how it gets there. It
depends on if this app could branch out into other pieces, again stored
procedures make sure that access is the same. Lastly it depends on how
often the logic is going to change, stored procedures are easier to
change and test than a whole application.
So you see it really does depend.
Dick Goulet
Senior Oracle DBA
________________________________
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:
