Re:Introspected REST: An Alternative to REST and GraphQL
by jmakeig on Saturday November 10, 2018 @03:35PM
(#18423346)
REST allows for clients and servers to evolve independently. If you can constrain that you can probably design something significantly simpler. That’s not a shortcoming of REST, though. The channel between your mobile client and your backend would probably be better served with something more like RPC than academic REST.
[ Parent
| on HN ]
Re:Introspected REST: An Alternative to REST and GraphQL
by vasilakisfil on Sunday November 11, 2018 @04:41AM
(#18425624)
That's our proposal/challenge here, come up with a model that tries to merry the best of both world (RPC and REST) but still adheres to HTTP semantics and allow clients/servers to evolve independently.