Comments on: Is Compression the Solution for Bloated XML in SOA? No

By: boomhauer

boomhauer — Mon, 07 Jul 2008 01:35:55 +0000

Sorry but this argument is worn out and invalid. My recent app required to download several thousand “rows” of data from a data store. My choice: 2.5 megs in raw xml over a webservice, or 100kb for the binary version of it. Please explain how i design around this. Easy to preach “good design”, much harder to practice with this level of limitations.

By: » Can good design compensate for XML bloat? | Service-Oriented Architecture | ZDNet.com

Tue, 22 Aug 2006 21:15:34 +0000

[...] In this new post, Sachin Garg picks up on this theme with a thoughtful discussion of the options pertaining to XML compression. Garg agrees with the line of thinking that "problems which can and should be solved by better design should not get patched by using compression or binary formats." He adds that even though he is a "data compression enthusiast," other options need to be looked at for SOA: "XML compression can be really great to ‘patch up’ the inefficiencies faced by SOA applications in handling large XML payloads, and fortunately there are solutions available. But nothing beats good design which can eliminate the problem at source." [...]

By: Sachin Garg

Sachin Garg — Sun, 20 Aug 2006 21:59:51 +0000

Thanks for the links Matt, XML ofcourse has its limitations and the alternates are welcomed.

But irresponsible designs and bloated documents cannot be blamed on XML’s limitations. My guess is that Dave’s concern (in the original ZDNet post) is that problems which can and should be solved by better design should not get patched by using compression or binary formats.

By: Matt

Matt — Sun, 20 Aug 2006 21:35:34 +0000

Good design will not solve the problems inherent with xml

http://www.idealliance.org/proceedings/xml...
http://www.w3.org/TR/xbc-properties/