From: Toon Koppelaars

To: Editorial

Date: 3 Nov 2004

 

Found this at www.theserverside.com a Java community site.

 

For me, a Java architect, Database is a persistence layer. Why should I have Business Logic (!) in a persistence layer? I don't want to know ANYTHING about my persistence layer, except that it stores data persistently. My business logic should have NOTHING to do with it!

 

 

From: Fabian Pascal

To: Toon Koppelaars

 

"Java architect" my foot. Everybody's an architect these days. He's a programmer -- that is, a building contractor in construction terms -- who does not know zilch about architecture, that is, data management.

 

 

From: TK

 

There is (much) more to be found (not to your surprise I am sure).

 

An article of mine dealing with implementing data logic (i.e. data integrity constraints) inside the database where they belong, and not in some application server Java-environment,  got posted at theserverside.com a month ago. Sort of throwing a freshly slaughtered lamb in front of a pack of hungry lions.

 

No need to say that the whole Java community reacted on this: see the discussion thread at http://www.theserverside.com/news/thread.tss?thread_id=29140 (the quote originates from there).

 

My conclusion: the way we do software application development these days, has definitely moved in the wrong direction, and we are all creating a huge software maintenance problem for the decade(s) to come.

 

And, as you have stated many times, it really is much worse than we all think.

 

 

From: Fabian Pascal

 

It is not the wrong direction, it is backwards. This is what we used to do before we had databases, and databases were invented to solve this very problem. But nobody knows that today, and they keep reinventing the square wheels that we got rid of 30-40 years ago. And this problem is endemic in the society at large; the US and the west have started their descent. It's over.

 

 

Posted 11/26/04