> An architect I closely work with always says: ‘Each extra component
> introduces complexity’. I think that is true. Each component ‘in the
> middle’ makes a system harder to understand, debug, maintain, deploy and
> requires an additional level of competence. Unless it has true added
> value,
> one should think very delicately if this extra component is really
> necessary.
>
The problem with this statement is that there will *always* be a
component in the middle, whether you think of FDS as middleware or not. It
is not a question of whether to put something in the middle or not, but a
question of *which* middleware to use.
> Actually, there is some contradiction in your last paragraph. You admit
> that
> putting middleware in place needs thorough testing (which costs money ...
> probably much more than the 20k you pay for FDS) and is a ‘daunting task’
>
> (which means that you are aware of the extra complexity and the risks that
> it brings). You actually mention the exact reasons why I would not like
> putting middleware in place for just one single client.
>
You misread him. What he said is that *installing FDS* requires thorough
testing which can be a daunting task.
ryanm
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
