July 2007 Archives

More RESTful clarity

| No Comments | No TrackBacks

So I talked, well actually chatted via instant-messaging, with Steve Vinoski and I do need to clear up some points from my last blog entry.

Steve pointed out that RPC does NOT require synchronous communications. This is true. One can simulate the request-response of a remote procedure using asynchronous communications. But the idea is that RPC appear synchronous - like a programming language procedure that blocks.

Some synchronous technology can appear asynchronous. E.g. CORBA has oneway operations. And many queue based (messaging) technologies use connection based technology underneath. E.g. Some publish subscribe technologies are actually connection based. The publisher connects to the notification service and so does the subscriber when retrieving messages. They are asynchronous to the application in the sense that they are decoupled.


Shame on me for not delving into this deeper, sooner. It was high time I took on some of the myths in the REST community again.

First let me say that I like REST. I think the architecture makes a lot of sense in many cases and I look forward to implementing my first RESTful services(s). Having said that the REST community don't do themselves many favors with the enterprise community, especially those that have been around the block several times and have built several flavors of architectures over the years. We know our architectures -we know our terminology. It seems the REST guys confuse some terms. So I'm going to target some areas to help unravel the muddle.


This article should have started "sitting here at the Ballmer's keynote at Microsoft's Worldwide Partner Conference in Denver". Instead, I'm writing it from my home office a day late before I head back up.

Before I start I need to point out that I work with Microsoft in their partner program. I'm committed to that. Microsoft technologies and products play a big part in the enterprise and will continue to do so. It's not going away. Microsoft often have some "negative" things to say about certain products etc. of their partners so I think it's okay for me to be critical if it's constructive and can lead to better products. (Also see the disclaimer about these being my opinions and not that of my company on the right ;-)


Who is IPBabble

William Henry IP Babble is the personal blog of William Henry.

William has 20 years experience in software development and distributed computing and holds a M.Sc from Dublin City University. He is currently working in the office of CTO at Red Hat on the MRG product. This weblog is not funded by Red Hat.

Posts are intended to express independent points of view, but understand that there is probably a bias based on the influence of working with standards based middleware for over a decade. (See disclaimer below)

December 2008

Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      

Disclaimer

The views expressed in this blog are solely the personal views of the author and DO NOT represent the views of his employer or any third party.

About this Archive

This page is an archive of entries from July 2007 listed from newest to oldest.

June 2007 is the previous archive.

September 2008 is the next archive.

Find recent content on the main index or look in the archives to find all content.