Re: Transaction Oriented Architecture (TOA)

H. S. Lahman wrote:
Responding to Gagne...

It seems to me the article was most of the way there when it proposes
things like isolating SQL so it is not embedded in the problem solution


I have to disagree with such advice. Isolating SQL is oversold. One
does not swap database vendors often enough to make it worthwhile.
Maybe if you sell a product that is designed to be used by multiple
DB's, such makes sense; but not for most custom apps. It creates more
work and more red-tape. (We have spent gazillion messages on this topic
before.)


and emphasizing low coupling between modules.

I've found "coupling" to be a rather subjective property such that it
is a nearly useless catch-phrase these days. (That is until the point
somebody defines it clearly and not tied to subjective criteria, such
as what app part is more likely to change.)

It just didn't say
specifically that one needs to encapsulate database access in a
subsystem behind an interface to do that. B-)


*************
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman

-T-

.