Re: Put code inside or outside database?

On Fri, 08 Apr 2005 06:45:19 -0700, GeoPappas interested us by writing:

> I was wondering what your opinion on this subject was...
 

Opinion only, as it will change dramatically based on technical reasons (computers, network, internationalization, language requirements, etc.) and politics ...

1. Put all data constraints in the database
   • never have to duplicate them in code
   • use declarative constraints as much as possible
2. Put business rules in database
   • never have to duplicate them (saves maintenance $)
   • use stored procedures
   • check whether invoking SPs using triggers is appropriate
3. Put all UI stuff elsewhere (JSP and Servlets in my case)
4. Never use EJBs (See "Better, Faster, Lighter Java" for reasoning).
5. Always look at the engine in depth to see whether there is stuff that you don't have to duplicate. Based on my analysis, it is generally FAR cheaper to [lock in to a vendor for 3 years, and then retrain and rewrite], than to do a [vendor independent shmoz of code that doesn't perform, that needs initial development (even though it's already in the vendor's product) and that needs ongoing maintenance] for things like Oracle's intermedia, locator, ultrasearch, message queueing, XA, etc.

Of course, the above may not apply to your situation.

-- 
Hans Forbrich                           
Canada-wide Oracle training and consulting
mailto: Fuzzy.GreyBeard_at_gmail.com   
*** I no longer assist with top-posted newsgroup queries ***