Tracking change and innovation in the enterprise software development community
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Recorded at:
Presented by Obie Fernandez on Jul 31, 2008
Right Collaboration Architecture Drives Business Transformation
Consolidation and Virtualization Are NOT Enough: The Case for Non-x86
The 5 Mandates of Software Development Teams - Presto Manifesto
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
I'm having trouble getting this video to play.It has also managed to crash firefox3 and IE 6.
Interesting ... with the same laptop, it works when outside the corporate network.
Obie: thanks for this interesting talk. There is definitely a lot of thinking behind it. If I understand the core of your argument, you are able to replace a typical action invoked from the controller by a combination of HTTP verb and a noun. So instead of login/logout you create/delete a session resource, instead of reserving something you create a reservation resource, and so on... The question I have is what do you gain in doing that. Unfortunately you mentioned in the talk that it was not part of your scope to talk about the implementation. If I try to imagine a new bid resource posted to an auction/bids I am wondering how different your implementation look like? aren't you mapping back from the resource representation to an action (say a stored procedure)? Resources are "navigational" in nature, they are not "relational", in other words when a resource (representation) embeds a link to another resource, there is absolutely no way to "navigate" back from the target resource to the source resource, unless you also add a link there. This means in particular that if you truly transform an action into a physical resource creation, you would have to "search" these resources to understand the state in which the parent resource is (remember that when you are posting a session, you are not doing a PUT to the user to change its state to "logged in"). So to figure out if you, as a user are logged in, you would have to search the "sessions" for one that matches your profile. To know if something is reserved, you'll have to search the reservations and figure out if one matches to thing being reserved, and so on... If on the other hand you are converting RESTful actions (HTTP verbs + nouns) into a store procedure call or a SQL statement, what have you gained? I don't buy the "cacheability" argument because I don't know many enterprises that would "cache" the content of a bank account or an insurance policy. I don't buy the HATEOS benefit either, because as you very well know in MVC there is the annoying path where the model needs to update the view because something has changed in the back-end. Again in the enterprise things happen in the back-end. As a matter of fact, I was a bit surprised that in your talk you did not really mentioned HATEOS and that the "actions" seemed to be a bit "external" to the resource representations, which IMHO would be an anti-pattern for REST. thanks, JJ-
Could you please make the slide deck available for download?
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.
4 comments
Watch Thread Reply