Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Posted by Stefan Tilkov on Nov 21, 2006
With a very funny blog post, written in the form of a dialogue between a Web services expert and a hypothetical developer, Pete Lacey has started an amazing chain of postings. Here is quick excerpt, but be sure to read the whole post ("SG" stands for "SOAP guy"):
SG: Forget what I said. From here on in we pass around coarse-grained messages—you like that term, coarse-grained?. Messages that conform to an XML Schema. We call the new style Document/Literal and the old style RPC/Encoded.
Dev: XML Schema?
SG: Oh, it’s all the rage. Next big thing. Take a look.
Dev: (Reads XML Schema spec). Saints preserve us! Alexander the Great couldn’t unravel that.
Among the many industry luminaries linking to Pete's post are Nelson Minar, who designed the SOAP-based Google APIs for both Google's search AdWords and says he'd never choose SOAP and WSDL again, IBM's Sam Ruby, who shows that REST as an alternative to SOAP is not without (fixable) problems, Sun's Tim Bray, and Ruby on Rails creator David Heinemeier Hansson.
Bill de hÓra's comment is a nice RESTafarian summary:
Which is worse, that everyone gets it now and we'll have REST startups in Q207, or that it took half a decade?
Free $40 SOA Demystified Book Offer
Right Collaboration Architecture Drives Business Transformation
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
Restful BPM, Pragmatic SOA, Mashups, Avoiding Failure: SOA track @ QCon London in March
Visit SOA Appliance Comparison Site
*Video Usage Model Tutorials
*Comparison to IBM DataPower X150
*Performance Benchmarks/Webinars
*Replace DataPower Program
FREE 1:1 Swap & Migration Services
>Which is worse, that everyone gets it now and we'll have REST startups in Q207, or that it took half a decade?
Unfortunately, even that may be a false choice. My experience is that not everyone gets it now... so it's actually worse than either of those alternatives, sadly.
I'm not suggesting that SOAP is the wrong choice for all cases (sometimes you don't control the choice of protocol between you and your collaborators), but it's just that when it clearly *is* the wrong choice, it's still too often the first tool to come out of the toolbox, as if it were the only one available.
While you're certainly right that there is still a lot of people who don't "get it", I do think that there's a lot more acceptance than, say, two years ago. Back then, even considering REST was considered weird ...
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
2 comments
Watch Thread Reply