• To: xml-dev@l...
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: "Andrzej Jan Taramina" <andrzej@c...>
• Date: Thu, 07 Apr 2005 12:30:55 -0400
• In-reply-to: <4253AFAF.7050804@l...>
• Organization: Chaeron Corporation
• Priority: normal
• Reply-to: andrzej@c...

Hmmmm, what Does SOAP/WS Do that A REST System Can't?

Lots:

1) Provides big vendors with new vendor lock-in and marketing spin 
opportunities.

2) Adds additional complexity and obfuscation that are unnecessary in many 
circumstances.

3) Adds a lot of overhead.

4) Provides a marked reduction in scalability, especially when used by the 
unwashed masses as an RPC mechanism.

5) Highlights the beauty of KISS-based approaches.

6) Lets you create an acronym that has no formal expansion, which sounds like 
an oxymoron.

7) Gives the XML-Dev group, and the industry as a whole, lots to 
discuss/argue about.

8) Opens up the door to silly questions.

<grins/>

Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

• References:
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Leigh Dodds <leigh@l...>

• Prev by Date: Re: Open source request....
• Next by Date: RE: XML Performance Improvements throughInterdisciplinary Factor Assessment and Application
• Previous by thread: Re: What Does SOAP/WS Do that A REST System Can't?
• Next by thread: Exposing resources/services vs hiding implementation details
• Index(es):
  • Date
  • Thread