3 ms·
I've given up on REST and I build all my new APIs with JSON-RPC. https://www.jsonrpc.org/specification https://www.jsonrpc.org/specification Super simple. I'm
by francislavoie 5y ago
I've given up on REST and I build all my new APIs with JSON-RPC. https://www.jsonrpc.org/specification https://www.jsonrpc.org/specification Super simple.
I'm not a fan of the complexity things like gRPC introduce to most languages (the PHP tooling is horrible for example), and I really don't like the limitations of HTTP verbs and the box that trying to confirm to CRUD puts you in.
- guggle 5y agoI second this (although I'd just stick with JSON-RPC 1.0). REST has its uses case, but alas it's now so ubiquitous that developers don't even think about wether they should or should not use it. For machine to machine communication between heterogenous systems, the simplicity of JSON-RPC means one can implement a client easily in any language. Also creating method stubs is trivial. The payload is still human-readable should you use it from the browser and it's not prone to debates and interpretations around the meaning of HTTP verbs. All you have to know is what method you want to call and with what arguments... something that is natural to all developers, while they almost always get the endpoints/resources/verbs thing wrong.
- lloydatkinson 5y ago> Updated: 2013-01-04 I'll pass...
- francislavoie 5y agoI don't see how that's a problem. There hasn't needed to be any updates to the spec. It's simple and it works.