public marks

PUBLIC MARKS from nhoizey with tags rest & architecture

2009

SOA is Dead

SOA was supposed to reduce costs and increase agility on a massive scale. Except in rare situations, SOA has failed to deliver its promised benefits. After investing millions, IT systems are no better than before.

2008

InfoQ: Hypermedia in RESTful applications

Flickr's current approach of requiring that clients possess Flickr-specific knowledge in order to progress from one application state to another, is simply another way of saying that they have a proprietary application model. Not only is it proprietary th

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.

2007

L'architecture orientée ressource pour faire des services web RESTful - Biologeek : Ubuntu, bio-informatique et geekeries libres d'un bio-informaticien au quotidien.

by 7 others
Le plus gros défaut de REST, c'est sûrement de se limiter à la comparaison des 4 verbes HTTP (GET, POST, PUT et DELETE) aux 4 actions possibles sur des données issues de bases de données (Retrieve, Create, Update et Delete soit CRUD)

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.

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

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.

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.