Skip to main content


Showing posts from September, 2009


For decades, XML remained as the only choice of communication / data transformation across layers in any applications that are architected based on services. It opened doors for many possibilities like inter-operable communications across different platforms. With the maturity of the platforms & products, average XML message size bloated because of lots of metadata & info related to security, transaction etc. The structure of XML is simple, elegant & human readable. But for consumers like applications codes, it is not a must for a communication mechanism to be human readable.

With the no. of applications using AJAX is increasing, especially in the case of RIAs, JSON replaced XML as the primary choice. This is becoming significant with applications shifting from SOAP-RPC to Restful services.

Why JSON is becoming so important:

• JSON can be easily handled by the AJAX / JavaScript clients than XML
• It is more lightweight than XML & hence high performing


It is common that whenever we talk about SOA, immedietly our discussion will jump into web services, SOAP, WS-* etc. In fact, for many of the techies, SOA mean SOAP and web services. They very rarely give due weighatge to the business side of it. Interestingly, in the recent days more awareness about significance of HTTP in SOA is growing and hence it resulted in more adoption of RESTful services for service enabling applications & business logic than sticking to SOAP/RPC web services. The XML metadata information and SOAP headers associated with webservices are considered to be an overhead than the HTTP headers. When HTTP itself is providing all facilities for an efficient, secured consumption of business logic & data, contractual SOAP web services is loosing its position as a key technology option for enabling services. It is witnessed by the fact that key players in the web like Google, Amazon, Digg, Flickr & Twitter are exposing RESTful services.

Plain Old XML (POX) and…