public marks

PUBLIC MARKS from nhoizey with tags soap & architecture

March 2008

REST vs. SOAP at Amazon

Amazon has both SOAP and REST interfaces to their web services, and 85% of their usage is of the REST interface. Despite all of the corporate hype over the SOAP stack, this is pretty compelling evidence that developers like the simpler REST approach.

October 2007

Pete Lacey’s Weblog :: What is SOA?

Once again the participants in the SOA discussion group have got themselves all riled up about what exactly SOA is and why it may or may not be working.

July 2007

REST vs. WS-*: War is Over (If You Want It) :: David Chappell :: Blog

by 1 other
REST is for data-oriented applications that focus on create/read/update/delete scenarios. Solution based on WS-* for service/method-oriented applications, especially those that need more advanced behaviors such as transactions and more-than-basic security

July 2006

» Amazon's SOA strategy: 'just do it' | Service-Oriented Architecture | ZDNet.com

It doesn't matter if a partner uses REST or SOAP, he pointed out. "Our developers don't care if it's REST or SOAP. It's all about customers," he said.

March 2006

REST wins, no-one goes home [@lesscode.org]

(via)
Let’s be realistic. No software architecture can truly withstand implementation. REST is really great, but on the web, there is plenty of detail work to be cleared out, like push, containership, encoding, side-effected GETs, curse-of-popularity, queuing, 2 versus 4 methods, universal format junk, and authentication, among others. I could go on, it’s messy out there.