Tracking change and innovation in the enterprise software development community
Testing Tools to
Support Agile
Software Delivery
Whitepaper
Recorded at:
Posted by Jim Webber on Oct 29, 2008 10:09 AM
Create REST-enabled Web Applications
Create a photo album application with Project Zero and REST design principles
Introducing IBM WebSphere sMash, Part 1: Build RESTful services for your Web application
Sponsored by 
What technology do you use for implementing your SOA?
This is a good REST presentation to understand its potential. But when you imagine to implement it for any real world enterprise systems you need to take care of some of the important aspects like transaction, reliability, etc. This presentation fails to cover those topics.
Hi Prashant,
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.
HTH.
Jim
Wonderful presentation Jim. You make hard topic easy. I'm a civil engineer turned into a web application developer by choice. People like me (who do not have C.Sc. degree) will benifit from your easy presentation.
Thanks.
Iqbal
Hi Jim,
You talked about micro format. Can you provide us with some links to this subject?
Thanks.
Iqbal
Some time ago I built a small WebDAV Access Point. While building it I had a very clear feeling that HTTP with its verbs and statuses was all I needed to build a transactional app. As part of that endeavour I built what was natural for WebDAV - bridge to documents and folders. But then I clearly saw how I could extend the capabilities of that little proxy tool for documents to also support CRUD operations for defects, tasks, etc. (it was a project management type of system that I built a bridge for). I even gave it a shot to see if it was really that easy to build it working right on the HTTP abstraction level but quickly gave up. Not because HTTP failed me. Simply because my work targeted MS Explorer as the only client and WebDAV response had no way of extending Explorer behaviour, I just could not expose "new" features to the end user; mapping them to the HTTP semantics was not an issue.
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
Hi Jim,
Excellent presentation-- very insightful.
Can one get the slides somehow?
Thank you,
-Javaid
Charles Nutter discusses bringing JRuby to the JVM, why Ruby is hard to implement, JIT compilation, precompilation, core Ruby implementation, Java library access, library challenges and future plans.
Alois Reitbauer specifies several architectural anti-patterns that one should stay away from and which can downgrade an application’s performance.
Teams in large organizations still struggle to adopt TDD. In this article Mark Levison shares problems he uncovered when he surveyed teams, and his own strategy to introduce TDD into an organization.
In this talk from RubyFringe, Luke Francl asks: is developer-driven testing really the best way to find software defects? Or is the emphasis on testing and test coverage barking up the wrong tree?
John Pampuch discusses the HotSpot compiler, the history of Java performance, HotSpot development philosophies and challenges, optimization, JVM library improvements, and tips for better performance.
In this interview, Keith Braithwaite, an Agile developer, consultant and trainer, says that we should show a good deal of skepticism towards today’s Agile practice.
This article demonstrates how to build and orchestrate highly configurable and extensible yet light-weight embedded process flow using AOP techniques with Spring AOP and Aspect J.
Jeff Patton explains why one needs to embrace uncertainty in order to succeed with his/her Agile project and how to avoid some of the common mistakes leading to project failure.
6 comments
Reply