In this presentation, recorded at QCon San Francisco, ThoughtWorks director of professional services and all-around Web and Web services expert Jim Webber explains the core concepts of message-oriented web services, expresses his thorough dislike of WSDL, explains different approaches to Web architecture, and shows an example of a RESTful workflow.
Dr. Jim Webber is director of professional services for ThoughtWorks, where he works on distributed systems for clients worldwide. He has extensive Web Services architecture and development experience and was the lead developer with Hewlett-Packard on the industry's first Web Services Transaction solution and is co-author of the book "Developing Enterprise Web Services - An Architect's Guide".
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community.QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Good presentation but lacks the practical touch
Re: Good presentation but lacks the practical touch
You're right, these are important topics and they cannot be wedged into a single talk. On the upside, they are all in my forthcoming book on Web integration. In the meantime, here's a minimal set of answers to your points:
1. Transactions - Don't use them, or at least not to cross service boundaries. Use other patterns to get consistent state updates (after all the whole REST thing is about state so it's a good tool for that job);
2. Reliability - Safety and idempotence deal with this on the Web. Retries are valid, and the metadata you get from interacting with a service helps with recovery scenarios. Don't underestimate the utility of safe GETs.
Great RESTful Talks
You talked about micro format. Can you provide us with some links to this subject?
I don't see WebDAV talked about much but it is a nice resource-oriented HTTP-based XML-driven protocol that has been out there for quite a while. Definitely not ready to be an integration services protocol but a good proof that the concept presented by Jim is perfectly viable.
Nice talk, thanks a lot