[
Lists Home |
Date Index |
Thread Index
]
An interesting article Len. Thanks for bringing it forward.
This fellow Arun makes some interesting arguments. Perhaps I am not fully
understanding, but the following three paragraphs, I perceive, are
representative of his arguments:
"By rushing headlong into XML, whose life-span is rather short (it has not
been around for 30
years) we are rushing like fools where angels fear to tread ... and we do
not understand the full effects of XML'izing or when things should be
XML'ized..."
"XML is used in service-oriented systems with *success* [but] none of them
are time or mission critical. Yet there are significant problems with using
XML."
"The laws of large networks are very different and the problems, a-priori,
cannot be formally analyzed by any means known today to even approach
predictive performance metrics... XML may have a butterfly effect in one
system, and cause failure (example, telephony) in another and yet may in
another system prove to be a real boon (example: XSLT transformation within
a system for business process management)."
This is my summary of his arguments:
1. XML is a relatively new technology.
2. XML may be useful in Web Services, however, there is no demonstration of
its utility in time or mission critical Web Services.
3. When considering the whole system (i.e., the Internet) the XML explosion
may have unintended consequences in remote areas of the system.
I was particularly intrigued by his usage of the term: "The XML Butterfly
Effect".
Len, you have a better grasp of Complex Systems than anyone I know. From a
Complex System's perspective, what are your thoughts about Arun's
statements?
/Roger
|
