Link Details

SOAP is heavyweight, while REST is light and mobile-friendly. However, there is another key difference which is often overlooked . . .

Posted by egenesky  |   Nov 30 2012 / 09:50

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Comments

User 237890 avatar

splatch replied ago:

It's direct presentation of product with no arguments or even samples (in code) why SOAP would be harder than REST. In fact both are related more or less to HTTP.

Reply 1 votes
User 221312 avatar

Riccardo Cossu replied ago:

Well, comparing a good REST API with any SOAP service layer doesn't seems fair: I mean, it is just as easy to simply add a SOAP layer over an existing service layer as it is to expose it through REST-like interfaces (i.e. using a lightweight layer instead of SOAP). What's difficult in a good REST architecture is to completely review the service layer to turn it from a procedure oriented architecture (which can be created with SOAP or other means) into a resource oriented one, which usually means totally rewriting the service layer.

Reply 0 votes
User 388907 avatar

MCII replied ago:

Its actually the opposite: It is DIFFICULT to create SOAP Web Services, but EASY to consume them.

Reply 0 votes

Recommended Links

Upvoters (4)



Downvoters (3)



Scala
Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Play
  3. Akka
  4. Debugging JavaScript
  5. Design Patterns
  1. Apache Hadoop
  2. REST
  3. Java
  4. Git
  5. Java Performance
Connect with DZone