search

interledger / interledger-rs

An easy-to-use, high-performance Interledger implementation written in Rust
http://interledger.rs
Other
201 stars 70 forks source link

Should we add a gRPC version of the HTTP API? #418

Open emschwartz opened 5 years ago

emschwartz commented 5 years ago

Note: worth looking at:

keefertaylor commented 5 years ago

I think the answer is 'yes', especially if we're investing in gRPC support in rippled.

Generally, I think that Ripple / Xpring should push the same suite of technologies across all of our APIs so there's a cohesive development experience (and internally, engineers can develop institutional knowledge more easily).

A one time investment here saves a bunch of time when you want to build out clients and tools. I would also suggest that you will save a lot of effort in maintaining these APIs because of the backwards compatibility and self documenting schema benefits.

Lastly, I think that generated code with method names and proper objects makes it easier for developers who don't have context to get started with your APIs (as opposed to manually prodding a JSON API or trawling through documentation).

I assume this is more of a philosophical question than a technical one. I'm happy to elaborate on the technical merits of gRPC over a JSON API (typing, code generation, compatibility) if it contributes to the discussion.

gakonst commented 4 years ago

Tonic got a 0.1 release: https://luciofran.co/tonic-0-1-release/