Finally, it seems Gartner starts recommending REST ("WOA") officially. Nick Gall writes:
Because of such consensus, the note can put forward Gartner positions such as:
- Interfaces based on WS-* specifications should be constrained by WOA, especially the generic interface constraints.
- More often than not, the WS-* protocol toolkit is unconsciously misused to create needlessly specialized interfaces.
- Application neutrality should be the principal goal of an interface, and implementation neutrality should be a secondary goal.
While I can’t share the entire note with the blogosphere, I can share a couple of highlights — first and foremost the official Gartner definition of Web-Oriented Architecture:
WOA is an architectural substyle of SOA that integrates systems and users via a web of globally linked hypermedia based on the architecture of the Web. This architecture emphasizes generality of interfaces (UIs and APIs) to achieve global network effects through five fundamental generic interface constraints:
- Identification of resources
- Manipulation of resources through representations
- Self-descriptive messages
- Hypermedia as the engine of application state
- Application neutrality
It's great to see this because it will definitely raise awareness about REST – whatever it's called – in large enterprises that are influenced by Gartner (i.e., almost all of them). I don't really buy the "WOA is different because it adds a fifth constraint" idea, but it's obvious that Gartner needs to continue inventing new terms to be innovative :-)
See http://www.valleyofthegeeks.com/News/GartnerQuadrant.html for an explanation of all Gartner related activity…