undefined | Better HN

0 pointsdragonwriter7y ago0 comments

> REST's shortcomings are the handful of endpoints required to get the information you actually want.

That's a problem of a naive CRUD API against a normalized relational datastore (or one structurally resembling such a store) regardless of architectural style, but there is no reason any standardized packet of information for which there is an expected recurring need should not be conceptualized as a resource in a REST API.

Orthogonality or normalization is not part of the REST architectural style.

0 comments

2 comments · 1 top-level

jonreem7y ago· 1 in thread

This approach necessitates an ever growing number of increasingly specific APIs, or an ever growing set of flags and options which will inevitably approximate a poorly implemented version of GraphQL.

iamjaredwalters7y ago

Exactly. Eventually eroding REST away to "RESTful".

j / k navigate · click thread line to collapse