pronto
grpcurl
pronto | grpcurl | |
---|---|---|
4 | 37 | |
6 | 10,141 | |
- | 1.4% | |
0.0 | 7.2 | |
over 3 years ago | 18 days ago | |
Java | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pronto
-
Buf raises $93M to deprecate REST/JSON
5. Message streaming (gRPC streams are amazing)
I can think of a whole host of features that can be built off of protos (I've even built ORMs off of protobuffs for simple things [0]). The value prop is there IMO. HTTP + json APIs are a local minima. The biggest concerns "I want to be able to view the data that is being sent back and forth" is a tooling consideration (curl ... isn't showing you the voltages from the physical layer, it is decoded). Buff is building that tooling.
[0] - https://github.com/CaperAi/pronto
-
Parsing Gigabytes of JSON per Second
I've written translation layers for such systems and it's not too bad. See this project from $job - 1: https://github.com/CaperAi/pronto
It allowed us to have a single model for storage in the DB, for sending between services, and syncing to edge devices.
-
gRPC for Microservices Communication
There's no reason you couldn't use gRPC with json as a serialized message format. For example grpc-gateway [0] provides a very effective way of mapping a gRPC concept to HTTP/JSON. The thing is, after moving to gRPC, I've never really felt a desire to move back to JSON. While it may be correct to say "parsing json is fast enough" it's important to note that there's a "for most use cases" after that. Parsing protos is fast enough for even more use cases. You also get streams which are amazing for APIs where you have to sync some large amounts of data (listing large collections from a DB for example) across two services.
With gRPC you also have a standardized middleware API that is implemented for "all" languages. The concepts cleanly map across multiple languages and types are mostly solved for you.
Adding to that you can easily define some conventions for a proto and make amazing libraries for your team. At a previous job I made this: https://github.com/CaperAi/pronto/
Made it super easy to prototype multiple services as if you mock a service backed by memory we could plop it into a DB with zero effort.
I think this "gRPC vs X" method of thinking isn't appropriate here because protos are more like a Object.prototype in JavaScript. They're a template for what you're sending. If you have the Message you want to send you can serialize that to JSON or read from JSON or XML or another propriety format and automatically get a host of cool features (pretty printing, serialization to text/binary, sending over the network, etc).
[0] - https://github.com/grpc-ecosystem/grpc-gateway
-
We Went All in on Sqlc/Pgx for Postgres and Go
I attempted to make something similar to this except the opposite direction at a previous job. It was called Pronto: https://github.com/CaperAi/pronto/
It allowed us to store and query Protos into MongoDB. It wasn't perfect (lots of issues) but the idea was rather than specifying custom models for all of our DB logic in our Java code we could write a proto and automatically and code could import that proto and read/write it into the database. This made building tooling to debug issues very easy and make it very simple to hide a DB behind a gRPC API.
The tool automated the boring stuff. I wish I could have extended this to have you define a service in a .proto and "compile" that into an ORM DAO-like thing automatically so you never need to worry about manually wiring that stuff ever again.
grpcurl
-
Roll your own auth with Rust and Protobuf
grpcurl
- Grpcurl: Like Curl, but for gRPC
-
Build and Deploy a gRPC-Web App Using Rust Tonic and React
The API server will be built and start running on port 50051. You can test the functionality using a gRPC client of your choice like grpcurl or Postman.
- download starlink stats
-
A detailed comparison of REST and gRPC
> What is the ubiquitous utility for interacting with gRPC? We have curl for REST. What is openAPI of gRPC?
grpcurl[1] combined with gRPC server reflection[2]. The schema is compiled into the server as an encoded proto which is exposed via server reflection, which grpcurl reads to send correctly encoded requests.
[1] https://github.com/fullstorydev/grpcurl
-
gRPC on the client side
The whole idea behind the post is that accessing the gRPC service with regular tools is impossible. To test, we need a dedicated tool nonetheless. I found grpcurl. Let's install it and use it to list available services:
-
RPC > REST
gRpcurl is a cool little tool to look at btw. Had to use it at my job before. Can call a gRPC via a curl like command. Regular curl doesn't support HTTP2. Had to use TLS with some tokens even. But you can reference a local .proto(gRPC protobuf file for the call) and make things easier for yourself if you hate reading instructions on command line args like I do.
- Show HN: ProtoCURL, a Curl for Protobuf
-
grpc-nvim: A simple GRPC client
A simple GRPC client built using grpcurl.
-
Traffic routing based on header value not working in gRPC service
Try testing with grpcurl, using the -H or -rpc-header flags to set the appropriate header.
What are some alternatives?
simd-json - Rust port of simdjson
bloomrpc - Former GUI client for gRPC services. No longer maintained.
pike - Generate CRUD gRPC backends from single YAML description.
grpc-over-webrtc - gRPC over WebRTC
sqlparser-rs - Extensible SQL Lexer and Parser for Rust
grpc-web - gRPC for Web Clients
grpc-gateway - gRPC to JSON proxy generator following the gRPC HTTP spec
wrk - Modern HTTP benchmarking tool
pggen - A database first code generator focused on postgres
grpcui - An interactive web UI for gRPC, along the lines of postman
sqlite
Hey - HTTP load generator, ApacheBench (ab) replacement