Take the 2-minute tour ×  Given that RESTful web services are
all based around the sacred idea that "everything is represented
as resources and can be accessed by an address (URI)", this may
make sense for CRUD applications (all examples are about
listing/creating/updating/deleting entities). However, how about
other business logic like, for example, creating a simple
calculator RESTful service that has nothing to do with CRUD
operations? What can be a good design for such a REST service?
Secondly, what is the real advantage of using REST over SOAP if
the logic of SOAP already makes complete sense?  share|improve
this question So what exactly is your question? –  paulsm4 Nov
26 '11 at 0:11 add comment  2 Answers  up vote 4 down vote
accepted  A calculator service would be simple to model in a
RESTful manner. The "R" in "CRUD" stands for "read", and there's
no reason that "read" can't also mean "compute". So a simple
Reverse Polish calculator service could be accessed via GET:
GET https://calc.com/rpnCalc?3&