A little advice about business logic [message #568132] |
Tue, 09 October 2012 12:17 |
Amine
Messages: 376 Registered: March 2010
|
Senior Member |
|
|
Hi all,
I used to write PL/SQL packages every time I can.
I am agree with Tom Kyte when he says "The Database is my operating system". From my point of view, centralizing the business logic into the DB is the best way
to build successfull applications.
I had a discussion with an Java EE developper, and we were not at the same wave length about that : he said that buisiness logic should be encapsulated "into Java"
(i.e transactionnal operations will be done with Java).
I am not a Jave EE specialist (only a little SE) but once again, Tom Kyte mentions one time in AskTom that "a good Java program does no :insert, update, delete neither select".
We are moving our applications progressively from F&R 6i to F&R 11g then, may be, to ADF. I am a little bit confused with that, can you light the way for me ?
Thanks in advance,
Amine
|
|
|
|
|
|
|
|
Re: A little advice about business logic [message #568152 is a reply to message #568148] |
Tue, 09 October 2012 16:13 |
Amine
Messages: 376 Registered: March 2010
|
Senior Member |
|
|
here is Tom Kyte answer
Quote:here is my short reply:
business logic is fine in the middle tier.
*data logic*, stuff that manipulates data, should be in the *data*
tier. If you want reusable code - put it in the database - anything can
use and reuse that. want web services? push a button - we'll publish
it as a web service. need it in java, great, you have jdbc. need it in
php, ruby, perl, C, C++, whatever - great - they can all do it natively.
|
|
|