An excellent pieceappears in the latest issue of CMP's Network World that provides somesobering insights on the XML performance problem, and what IT professionals can doabout it until standards, specifications, and methods are wrung out of committees.
David Greenfield starts off with this provocativethought: "The next time the CTO speaks about Service-OrientedArchitectures(SOAs), remember this: XML, the technology underlying today's SOAs,consumes 30 to 50 times more bandwidth than comparable protocols, canincrease storage requirements tenfold, and may run a fraction of thespeed of traditional interapplication processes. So just how are yougoing to realize the CTO's vision of an SOA without killing thenetwork?"
He goes on to add that "The networking and security implications for deploying afull-blown SOAbased on XML and Web services are enormous. At every facet of theenterprise, network architects need to rethink the impact that such amove will have on their infrastructure."
Greenfield's take isthat XML processing will have to be pushed out to the network, tospecialized appliances. He goes on to provide a look at what exactlythese appliances are, and what they can and can't do.