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.
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.