REST vs SOAP Roll Call

Posted by Miko Matsumura on Aug 15, 2006

Sections

Architecture & Design,

Enterprise Architecture

Topics

SOA ,

Web Services ,

REST

Tags

SOAP

Stefan Tilkov on his blog has produced a useful roll call of REST vs SOAP/WS style bloggers

When designing SOA, it's important to consider appropriate architectural style--and themes from REST or from the Web Services community may be applicable depending on the requirement set. It's incumbent on architects to understand the advantages and disadvantages of both styles to better apply the techniques. This list of bloggers is very useful as a tool for exploring these styles. In particular, if you see yourself in one of these camps, it may be useful to peruse the "other" camp's blogs to gain an understanding of the benefits of such approaches.

Web Services/WS-* supporters (10)

• Chris Ferris
• Christian Weyer
• Eric Newcomer
• Hartmut Wilms
• Jeff Schneider
• Jorgen Thelin
• Richard Veryard
• Ron Ten-Hove
• Steve Jones
• Ted Neward

REST supporters (15)

• Bill de hÓra
• Carlos Perez
• Dare Obasanjo
• Elliotte Rusty Harold
• Joe Gregorio
• Mark Baker
• Mark Nottingham
• Mark Pilgrim
• Patrick Logan
• Paul Downey
• Sam Ruby
• Sean McGrath
• Steve Loughran
• Tim Bray
• Yaron Goland

Supporting both (15)

• Anne Thomas Manes
• Clemens Vasters
• Dave Orchard
• Don Box
• Doug Purdy
• Jim Webber
• Mark Little
• Mike Champion
• Loek Bakker
• Michael Platt
• Radovan Janecek
• Sanjiva Weerawarana
• Savas Parastatidis
• Steve Maine
• Steve Vinoski
• Werner Vogels

1. Back to top

   I'm not so much against REST..

   by Steve Jones

   As for sticking to one approach and standard, if REST had come first and done all the leg work around policy and security then that would be great too. But things like 802.11x and the US phone networks surely teach us that its much better to agree on a standard than have lots of twisty standards all different (which was what I blogged about a while back).
   
   IT is too obsessed with the next best thing, rather than just making do and using what is "good enough". We are the Golgafrinchans never getting anywhere because we argue what colour the wheel should be. Technical discussions like SOAP v REST add nothing to the debate as to how IT will better deliver business solutions that are maintainable, flexible and most importantly look like the business rather than a series of techy acronymns.

   Reply

2. Back to top

   REST vs SOAP Roll Call

   by Javier Castañón

   It could be interesting to build a list of REST-ian books and SOAP books. Or at least non SOAP books. I find Dirk Krafzig's Enterprise SOA: Service-Oriented Architecture Best Practices a non SOAP book, on the other hand Thomas Erl's Service-Oriented Architecture: Concepts, Technology, and Design is too SOAPy to my taste.
   
   Javier

   Reply

• Older >