InfoQ have posted a very interesting interview with Sanjiva Weerawarana which (if people actually bother to read and understand it) does shed some light on the seemingly never-ending REST/WS-* debate.
http://www.infoq.com/articles/sanjiva-rest-myths
The key point in the whole interview for me is this quote from Sanjiva, and which emphasising why REST-vs-WS-* ior REST-vs-SOA are spurious questions by comparing apples-to-oranges:
The real question is whether resource oriented architectures and service oriented architecture are one and the same. I assert that they're not: given a distributed systems problem one can develop solutions using either approach and the artifacts that result would be radically different.
This mirrors the theme of a presentation I gave 4 years ago pointing out some of the differences between resource-oriented and service-oriented architectires. and matched by some comments from that time acknowledging that, while I don't agree that REST is the "one-and-only-true-way" to write distributed systems, that there ARE indeed cases where REST is a good choice.
http://www.thearchitect.co.uk/presentations/arch-styles/3-arch-styles.pdf
Of course, I don't expect the fanatical RESTafarians to ever achnowledge the corollary - that there are indeed cases where "pure" SOA-style is a good choice, so I guess the cycle of war will continue to repeat itself!
All content is
Copyright (c) 2008 Jorgen Thelin. All rights reserved.
The opinions expressed here represent my own views
and not necessarily those of my current, prior or future employer(s).
Content is provided "as-is", without any representations or warrenties of any kind.
Contents of the Weblog Feed are
licensed under a
Creative Commons License.