CLOSE FULL VIEW
OpenStack Extensions: Challenges and Lessons Learned in the Development and Governance of Extensible REST Services
Recorded at:
- Share
-
- |
Read later
My Reading List
Bio
Jorge Williams is a Principal Architect in the Rackspace Cloud Integration Team where he develops tools and services to solve integration problems. He has aided in the design and development of the Repose HTTP proxy, the Cloud Servers API, the OpenStack Compute and Identity APIs, and the OpenStack extension mechanism.
The World’s Largest Conference Dedicated to SOA, Cloud Computing & Service Technologies.
Community comments
I am confused
by
Jean-Jacques Dubray
Posted
I am confused
by
Jean-Jacques Dubray
REST was sold to us because WS-* was too complex and all you would need was to expand the resource space or use hypermedia as you see fit. In particular, people like Steve Vinoski or Bill Burke kept telling us that because the interface to resources was "Uniform" you would be building non-breakable distributed application.
Now, you are telling us that because "RESTful" services can't support namespaces, we have to create a central registry of some kind of contract metadata. You are telling that extensibility is really hard to reach.
To me, HTTP headers sound like an obscure non RESTful kludge for dealing with extensions.
Looks like you could have done all this work with WS-* in a fraction of the time. Am I mistaken?
Now, you are telling us that because "RESTful" services can't support namespaces, we have to create a central registry of some kind of contract metadata. You are telling that extensibility is really hard to reach.
To me, HTTP headers sound like an obscure non RESTful kludge for dealing with extensions.
Looks like you could have done all this work with WS-* in a fraction of the time. Am I mistaken?
Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think