REST for session-based single-user service?

Question

I'm thinking about implementing a server for remotecontrolling a device as a RESTful service. Unlike most restful services known from the web it could only serve one client in a meaningful way at a time. Do you think that REST is still a valid option or would you see this single-user, session-based scenario as a sign to choose another way to interact remotely?

Answer 1

You could certainly follow many of the principles behind a REST architecture for your service, but it doesn't sounds like you really need most of them. REST is better suited for larger long lived systems with lots of disparate clients.

Now, HTTP, on the other hand, could easily be leveraged to create simple service for you needs. But, HTTP != REST. REST is an architecture, HTTP is a protocol.

Answer 2

The fact that it's so easy to implement is a win in my books. You can get rest services running in a matter of minutes to hours, depending on your expertise and framework choice, etc. It's very simple to consume with a variety of interfaces, giving it more points. When your service transitions into servicing multiple clients at a time, it becomes only more extensible and in your favor to have it.

There are other alternatives, but to me this seems like a perfectly valid route to take.