3 ms·
This has been bothering me for years. I don't understand why REST vs GraphQL are so often presented as the only options. My observation is 90% of APIs for syste
by tobyjsullivan 5y ago
This has been bothering me for years. I don't understand why REST vs GraphQL are so often presented as the only options. My observation is 90% of APIs for systems I've worked on should be using something more akin to RPC yet it doesn't even register in the conversation. I'm sure there are other great options too.
I've never seen an API on a project I've worked on that comes close to proper REST - and rightfully so as they'd never benefit.
- dragonwriter 5y ago> My observation is 90% of APIs for systems I've worked on should be using something more akin to RPC A lot of “REST” is something more akin to RPC, which is probably why those aren't broken out separately. REST only occasionally refers to anything resembling the architectural model described by Roy Fielding.
- jayd16 5y agoI don't know, I think gRPC is fairly common as well. Its not on the hype train because it doesn't move design control like GraphQL (which moved some API design control from backend to frontend devs.)