PUBLIC MARKS with tags rest & soa

Transfer Methods. This is at the core of REST and ROA and is the foundation of Web-Oriented Architecture. You can read Roy Fielding's chapter on REST (he conceived of the approach originally) or you can just follow the simple guidelines here. At other times, protocols like BitTorrent can be used if the requirements warrant it, but these are exceptional scenarios that I will cover at some point in the future.

Ne pas citer XMPP dans les "Transfer Methods" quelque jours après l'annonce de Google Wave, et surtout le mettre dans le schéma au niveau des Microformats fait perdre toute crédibilité à l'article.

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.

Livres Blancs et Cahiers disponibles gratuitement sur le site web de la société OCTO Technology.

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 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

To define and describe a web-service API, many developers would use WSDL. Although WSDL is meant to be extensible to any protocol and message format, most people use it for HTTP GET/POST and SOAP, when writing to WS-* standards. On the other hand, developers writing a REST API using XML over HTTP typically don't use WSDL, or any other standardized definition/description of the API.

using the basic Web formats and protocols such as HTTP, XML, REST, and JSON as the "Unix Pipe of the Web" -- to quote a colorful phrase of Ray Ozzie's -- as the fundamental glue between systems

my latest Internet Computing (IC) Toward Integration column tries to take a middle ground in the ongoing "REST vs. SOA" debate. It's called "REST Eye for the SOA Guy" (PDF) and it attempts to explain, from the perspective of someone like me with a lengthy SOA background, the benefits that REST brings to the distributed systems picture

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.