There are number of resources available on line, but I would like to hear a clear idea, on how we can differentiate a service as SOAP/REST by looking at service design? (not with wsdl/wadl)
How they differ in the architecture?
There are number of resources available on line, but I would like to hear a clear idea, on how we can differentiate a service as SOAP/REST by looking at service design? (not with wsdl/wadl)
How they differ in the architecture?
As an experienced user, you have probably read all the technical answers to similar questions already, such as this and this, so I will try a different kind of answer, a more metaphorical one.
Indeed, we can rephrase the REST vs SOAP debate, by looking at what is the main notion for each of them:
As an example, let's consider a book delivery service:
With SOAP, you are defining endpoints for actions. With REST, you provide endpoints for things.