If your business logic is in the client, and you need a backend data API, HTTP is an option. Just don’t call your static URI API “REST”.

Oct 12, 2015 · 7:06 PM UTC

5
18
1
12
Replying to @stilkov
@stilkov a little late to change HTTP API culture isn’t it? ;-)
1
1
@pvblivs I don’t think so, now is the perfect time. There’s a lot of adoption and a lot of interesting challenges ;-)
1
more replies
Replying to @stilkov
@stilkov My experience: JSON over HTTP is considered REST. Hypermedia is being considered academic nonsense. Which is sad and dumb.
1
@elgoodie There was a time when making a difference between GET and POST was considered academic nonsense, too. Let’s not give up yet.
Replying to @stilkov
@stilkov don't understand why you can't have a RESTful data API.
Replying to @stilkov
@stilkov I like the term “static URI data API over HTTP” to describe those non-REST APIs