[
Lists Home |
Date Index |
Thread Index
]
4/11/2002 10:59:48 AM, "Simon St.Laurent" <simonstl@simonstl.com> wrote:
>He also encouraged attendees to consider when building Web services
>whether to program to an object-centric or XML-centric model. One
>pitfall to look out for in the object-centric path is how to obtain
>extensibility when you are programming at a high level, he said....
I agree, that's a very thought-provoking piece. Another article I just noticed
yesterday is also well worth careful thought: Adam Bosworth on loosely coupled
architectures for web services.
http://www.fawcette.com/xmlmag/2002_04/magazine/departments/endtag/
"By loose coupling, I mean that you can be sure that changes to your implementation
will not break other applications that are relying on it through the aegis of Web
services. ... each application en-queues well-defined messages to the other
applications and de-queues well-defined messages from them. This model is ideal for
several reasons.
It is robust in the face of failure or delay. If another application happens to be
unavailable or taking a long time, the system will still work. No application will
become a single point of failure in the system. It is also robust in the face of
change or diversity. As long as the other applications continue to use the same
grammar for their messages and in the same order, they can change their
implementations over time or support totally different implementations. Finally, it
is manageable. Since messages tend to live in queues, they can be rerouted,
prioritized, and analyzed.
...
The only real success story to date in the world of loose coupling is the Web
itself. ... The only thing the browser knows is the wire format (usually HTML) and
the protocol."
|
