public marks

PUBLIC MARKS from nhoizey with tags "web services" & architecture

April 2007

SOA et Web Services : Questions / RÈponses

by 1 other
Des tonnes d'infos intéressantes sur SOA et les Web Services, par Pierre "Orchestra Networks" Bonnet

January 2007

Architecting Industry Standards for Service Orientation

Many messages that flow among businesses are formatted to specific industry standards. As we move toward Web services and service orientation the payloads can add value to the messaging infrastructure in a flexible, interoperable, composable way.

Service Architecture - SOA: Why Quality of Service depends on the Consumer and the Producer

(via)
it is actually not up to the server to purely dictate a straight process and response to the consumer it is up to the consumer and producer to negotiate the right result for both parties a QoS policy that assumes that the producer is the final arbiter of quality is liable to produce a very unfriendly service and one which doesn't interact with people in the manner which they wish

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.