Rules for REST API URI Design

Re:Rules for REST API URI Design by idkfa on Sunday June 18, 2017 @04:19AM (#14579608)

just drop this REST hype altogether and use adequate protocols for communication

[ Parent | on HN ]

Re:Rules for REST API URI Design by pyre on Sunday June 18, 2017 @04:34AM (#14579652)

As in design a custom TCP/IP protocol for every application?

[ Parent | on HN ]

Re:Rules for REST API URI Design by stingraycharles on Sunday June 18, 2017 @05:25AM (#14579798)

I think there are a few GraphQL enthusiasts entering this thread right now, which has its own merits, but can live perfectly next to REST.

[ Parent | on HN ]

Re:Rules for REST API URI Design by konschubert on Sunday June 18, 2017 @05:36AM (#14579836)

In my company we use graphql for getting, and REST for all other operations.

Might be an antipattern, but has served us well.

We're also using a special flavor of graphql that returns the data as flat dictionaries instead of deeply nested dictionaries. Whether you need that or not of course depends on the client design.

[ Parent | on HN ]

Re:Rules for REST API URI Design by kuschku on Sunday June 18, 2017 @05:28AM (#14579807)

As in using GraphQL for this purpose, I presume. Or even offering an SQL-API. Seems more ideal than overly complicated URL schemes.

[ Parent | on HN ]