Saturday, September 25, 2010



I started my "carreer" in Distributed Computing back in 1997, as a Forte and Visibroker specialist.

In Forte it was a matter of seconds to create a Distributed Object, deploy it to a cluster of servers, an create a client to invoke it.

When it came to integrate Forte with Java, I fell immediately in love with IDL and ORBs.
Visibroker was loaded with features, and it would come with a idl2java tool to create Java stubs and invoke a CORBA service.
At that time I was in Bangalore, and I used to spend all my weekends at office experimenting with ORBs. A thrilling experience.

13 years after,

IDL is gone and we have WSDLs and XSDs. IDL was simple, WSDL and XSDs are intricate.

IIOP is gone and we have SOAP. IIOP was fast, SOAP is as slow as molassa.

Performance is pathetic. Garbage collections through the roof.

Standars are multiple. Each vendor implements its own flavour.

Something went terribly wrong in the IT industry in the last 15 years.

Read about performance here

I am 100% with the author of this post. I have worked with both IDL and SOAP and the former was orders of magnitude better specified and easier to use. The only good point of SOAP is that you can manually carve your payload with notepad, but is this a good reason to build your Enterprise Solution on top of it? On the contrary, it seems to me a proof that most developers will simply tinker and carve hand-crafted messages which can or cannot work according to the SOAP implementation.

Luciano says that SOAP/WSDL is for the weak of mind, really cool people use REST + JSON. I will investigate the technology.

Here another rant against SOAP.

Every time I hear "SOAP and XML are cool" I kill a kitten.

No comments: