Last post Mar 22, 2013 10:56 PM by snskrishna
Mar 22, 2013 03:12 PM|atiliosud|LINK
For an e-commerce platform based on SOA,
what kind of architecture services would you recommend? SOAP or REST?
Mar 22, 2013 06:40 PM|sukumarraju|LINK
Mar 22, 2013 10:56 PM|snskrishna|LINK
It Should be SOAP, simple because it provides transaction management and enterprise featured security API which is you app (e-commerse)
to understand more study the following differences
<div style="direction: ltr;">
SOAP stands for Simple Object Access Protocol
REST stands for REpresentational State Transfer.
SOAP is a XML based messaging protocol
REST is not a protocol but an
SOAP has a standard specification
but there is none for REST.
Even SOAP based web services can be implemented in RESTful style.
Whole of the web works based on REST style architecture.
Consider a shared resource repository and consumers access the resources.
REST is a concept that does not tie with any protocols.
SOAP is distributed computing style
REST is web style
But SOAP doesn’t has any such requirements.
REST messages should be self-contained and should help consumer in controlling the interaction between provider and consumer
links in message to decide the next course of action)
SOAP is XML based message protocol.
REST does not enforces message format as XML or JSON or etc
SOAP has specifications for stateful implementation as well
REST follows stateless model
SOAP is strongly typed, has strict specification for every part of implementation
REST gives the concept and less restrictive about the implementation
Therefore REST based implementation is simple compared to SOAP and consumer understanding
SOAP uses interfaces and named operations to expose business logic
REST uses (generally) URI and methods like (GET, PUT, POST, DELETE) to expose resources
SOAP has a set of standard specifications.
WS-Security is the specification for security in the implementation. It is a detailed standard providing rules for security in application implementation. Like
this we have separate specifications for messaging, transactions, etc.
REST does not has dedicated concepts for each of these. REST predominantly relies on HTTPS
Above all both SOAP and REST depends on design and implementation of the application.
SOAP based reads cannot be cached.
REST has better performance and scalability. REST reads can be cached
While SOAP supports SSL (just like REST) it also supports WS-Security which adds some enterprise security features
Need ACID Transactions over a service, you’re going to need SOAP
While REST supports transactions, it isn’t as comprehensive and isn’t ACID compliant
SOAP brings it’s own protocol and focuses on exposing pieces of application logic (not data) as services. SOAP exposes operations. SOAP is focused on accessing named operations, each implement
some business logic through different interfaces.
RESTs sweet spot is when you are exposing a public API over the internet to handle CRUD operations on data. REST is focused on accessing named resources through a single consistent interface.