SOAP and SUVs
Loek Bakker makes an analogy, likening SOAP to SUVs.
Now the good thing about this analogy is that it holds a very clear lesson for when to use it: if you do not need the off-road capabilities or if you never flick the 4WD switch, probably you do not need an SUV. If you do not need the SOAP extension /WS-* possibilities or if you never make clever use of the SOAP header, probably you do not need SOAP services.
One might argue, though, that SUVs just create an illusion of being capable of off-road usage … if I needed one, I’d rather use a real off-road car than one that just resembles one.
I’d use a full suspension mountain bike and cut up the SUV the moment it got bumpy. While Landrovers can climb and do river crossings nicely, they lack the agility to do technical stuff and their centre of gravity is such that they can flip if you try and traverse the steep stuff.
The only time I’ve been overtaken by a motor vehicle on an offroad descent was in the french pyrenees, by farmers in an old renault van.
Ahh, but how about the ascent :-) And how well does your mountain bike keep you dry in the rain?
I kindof like this analogy even if so many people hate it. Your choice of, uhh, “transport protocol” depends on the job at hand. If it’s a nice day in those months where it is light at both ends of my commute, I ride my bike to work. If not, I take my old Honda. If it is snowing I take my wife’s AWD Subaru. I’m not going to get into any religious wars about whether the bike or the Subaru are “better”, just use the appropriate one for the job at hand. I know there are bike-afarians who will proudly put on their rain gear and ride every day, and SUV devotees who spend $10 a day on gas (they might rationalize) just in case it rains or they have to go off-road. Basically, they’re doing one or the other for reasons that have little to do with the pragmatics of how to get to work in reasonable comfort / safety at the lowest price, however, and there’s not much point in arguing.
Back to web services … people who do care about the pragmatics and don’t care about the dogma have a very similar choice between the lightweight, cheap approach that is very good for fair weather requirements (nothing bad happens if messages are lost or intercepted) but more of a challenge for heavy weather requirements (the smelly stuff happens if messages are lost, intercepted, misdirected, etc.). You can of course put on your rain gear (lots of application-level programming) and make the lightweight solution work, but I suspect that most sensible and successful implementers think, “hmm, lots of smart people have been thinking about the problems I’m having for 5 years now and all the big companies implement “WS-SUV”. What I don’t know is how well either actually succeeds in the real world.
So, for my plug: Please submit your experiences implementing either BIKEafarianism or WS-SUV as a proposal for a talk at the XML 2006 (Boston, in December) See http://2006.xmlconference.org/call-for-participation.html I’m thinking of the Enterprise XML track, but you may wish to go with another. It would be SO nice to bring some concrete evidence to this permathread.
It seems the car of choice for REStafarians is a little different: http://www.markbaker.ca/2001/04/Z8/
;-)
Mike Champion said:
“Back to web services … people who do care about the pragmatics and don’t care about the dogma have a very similar choice between the lightweight, cheap approach that is very good for fair weather requirements (nothing bad happens if messages are lost or intercepted) but more of a challenge for heavy weather requirements (the smelly stuff happens if messages are lost, intercepted, misdirected, etc.). “
Mike, can you please enumerate which specs you are talking about? And cite a couple impls?
And don’t say WS-RM because that doesn’t guarantee squat.
Cheers,
Mike
I’m thinking of the specs that are supported both by Microsoft WCF (“Indigo”) and Sun’s Project Tango. I don’t have the complete list handy but it should be be fairly easy to figure out. WS-ReliableMessaging is one of them. It doesn’t “guarantee squat” as far as actual message delivery, to be sure. It does guarantee that a failure to deliver a message will be reported to the sender, doesn’t it?
Anyway, don’t look to me for success stories for WS-SUV. I’m trying to get people who do have experiences one way or the other to talk about them at XML 2006.
Hmmm, you guys are discussing at the wrong blog, give me credits for my creative work on the analogy guys ;-). Anyways, I love the “WS-SUV” Mike C.!
Since I positive hate SUVs, I’m happy to give you credit for the invention ;-)
The question is then: how about SOAP services? Hate those too? ;-)