Re: Application logic and Business logic
From: topmind (topmind_at_technologist.com)
Date: 02/27/05
- Next message: topmind: "Re: Application logic and Business logic"
- Previous message: Dmitry A. Kazakov: "Re: creaping coupling......"
- In reply to: Patrick May: "Re: Application logic and Business logic"
- Next in thread: Patrick May: "Re: Application logic and Business logic"
- Reply: Patrick May: "Re: Application logic and Business logic"
- Reply: Thomas Gagne: "Re: Application logic and Business logic"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 27 Feb 2005 12:57:47 -0800
(* That's an interesting assertion. What evidence do you have to
support it? *)
"Decision math". The chances of switching to a different GUI or DB
vendor is relatively small compared to the cost of the extra separation
layers in terms of coding and maintenence. Add in the "future
discounting" from finance principles, and the the total weighs in favor
of not doing it.
Further, even if you do separate, often the feature set and philosophy
of new gui's is so different that you have to overhaul a bunch of stuff
anyhow.
Some justify it by saying that certain changes can all be done in one
spot, but they rarely consider the costs of changes that do not favor
that grouping. No grouping favors every change pattern. One has to
weigh the estimated probabilities of changes.
What is your justification for the wrapping? Wrapping is not the
default, so the burden of evidence is not really on me, BTW.
-T-
- Next message: topmind: "Re: Application logic and Business logic"
- Previous message: Dmitry A. Kazakov: "Re: creaping coupling......"
- In reply to: Patrick May: "Re: Application logic and Business logic"
- Next in thread: Patrick May: "Re: Application logic and Business logic"
- Reply: Patrick May: "Re: Application logic and Business logic"
- Reply: Thomas Gagne: "Re: Application logic and Business logic"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|