3 ms·
So why use REST at all at this point? What is the benefit REST is bringing to the table here? Seems like if you want a declarative API you might as well do so
by jayd16 7y ago
So why use REST at all at this point? What is the benefit REST is bringing to the table here?
Seems like if you want a declarative API you might as well do something like a local read replica a la Firebase. Seems like the natural progression of these API as single schema technologies.
Is the main reasons for sticking to REST here compatibility or is there something in the RESTful design we want to hold on to?
- z3t4 7y agoREST it pretty stupid, but it works over HTTP(S) and is state-less. And tools that use HTTP has nice abstraction layers already, and are very common, so it becomes simple to use. Personally for talking with a web front-end I would use Websocket's with long-polling as fallback. And use JSON instead of query-string for querying. It does however require yet an abstraction layer, and is more brittle and less secure then REST. REST is a school-bus. Other methods are like exotic sports-cars.
- jayd16 7y agoWell sure it's common but my question is whether that's the only reason. If we're going to down the path of declarative requests and the like, why not push it further like firebase has done? I'd prefer that a lot more if there was a self hosted/open source alternative.