Link Details

Link 885063 thumbnail
User 975993 avatar

By egenesky
via architects.dzone.com
Published: Nov 30 2012 / 09:50

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

Comments

Add your comment
User 237890 avatar

splatch replied ago:

1 votes Vote down Vote up Reply

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.

User 221312 avatar

Riccardo Cossu replied ago:

0 votes Vote down Vote up Reply

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.

User 388907 avatar

MCII replied ago:

0 votes Vote down Vote up Reply

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

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.

Voters For This Link (4)



Voters Against This Link (3)



Debugging JavaScript
Written by: Ashutosh Sharma
Featured Refcardz: Top Refcardz:
  1. Design Patterns
  2. OO JS
  3. Cont. Delivery
  4. Java EE7
  5. HTML5 Mobile
  1. Java EE7
  2. Spring Annotations
  3. Git
  4. Java
  5. REST