Dennis Sosnoski wrote:
> One of the major justifications I give for the widespread use of XML as
> the basis for message exchange in SOA is that the XML structure provides
> decoupling between client and server data structures - each end is free
> to work with the XML messages as they want, without concern over how the
> other end works. That seems to me to be an important criteria for SOA
> services.
I think that this is a fair representation of one advantage of XML. That
decoupling also represents a new form of investment because there is an
additional toolset and computational overhead investment that you have to "buy"
into as well. Evaluating your total costs really needs to be a step in your
SOA
design. If XML doesn't provide any direct benefits, it shouldn't be used.
Native language data exchanges and those already tooled into your development
platform, are often better and more effective solutions than those you get by
adding tools/app servers or other infrastructure expenses. When your vendors
app server goes away, you'll be looking for new toolsets, which will be an
added
cost.
Even open source things might not last forever from a support perspective, so
if
you don't include support costs, porting costs and other associated expenses
for
the tooling, focusing on standards based technologies doesn't gain you anything.
Gregg Wonderly
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> 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/
