top | item 31287271

(no title)

hatch_q | 3 years ago

In all honesty, we do this with REST now. Just define interface with OpenAPI - then create clients, servers in virtually any language you like.

discuss

order

francislavoie|3 years ago

The problem with REST for me is that it locks you to HTTP verbs and URIs. And it's not a great mapping for much more than CRUD. I find it really restrictive and annoying. It's specific to HTTP as the transport, so I can't use REST over websockets or some raw TCP server-to-server pipe, etc, without making a kludge of it.

dimgl|3 years ago

This is actually really cool! Any chance you can point me to an implementation for JSON-RPC? I'm interested to see the benefits with JSON-RPC over a traditional REST API.