News for hackers. Stuff that matters.

A comment on REST Anti-Patterns (2008). Parent comment

Re:REST Anti-Patterns (2008) by ben_jones on Wednesday May 10, 2017 @02:01PM (#14310205)
It just causes so much busy work. Then busy work leads to bugs, which leads to framework abstractions, which leads to implicit nuance in almost every part of web development.

RPC and client-server contracts, as well as static-typing, is a bloody god send and the whole world will be in a better place once we formalize and accept it (I didn't say standardize I said formalize).

[ Parent | on HN ]
Re:REST Anti-Patterns (2008) by michaelchisari on Wednesday May 10, 2017 @03:35PM (#14310947)
I'll defend REST's utility for simple data retrieval. If I just need a paginated list of comments on a video, being able to quickly hit /video/1093/comments and get that list back is really nice.

More complex use cases, and specifically non-idempotent operations, is where I find REST doesn't hold up as well as RPC.

[ Parent | on HN ]
Re:REST Anti-Patterns (2008) by naasking on Wednesday May 10, 2017 @08:19PM (#14312930)
> If I just need a paginated list of comments on a video, being able to quickly hit /video/1093/comments and get that list back is really nice.

REST isn't about human-readable URLs. The link to the comments should have been part of the representation returned for /video/1093 (typically JSON these days, so a "comments" property of the object).

[ Parent | on HN ]