Tracking change and innovation in the enterprise software development community
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Recorded at:
Presented by Jim Webber on Oct 29, 2008
Right Collaboration Architecture Drives Business Transformation
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
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
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.
6 comments
Watch Thread Reply