grpc-gateway
grpcurl
Our great sponsors
grpc-gateway | grpcurl | |
---|---|---|
30 | 37 | |
17,367 | 10,086 | |
1.2% | 2.6% | |
9.8 | 7.1 | |
about 14 hours ago | 14 days ago | |
Go | Go | |
BSD 3-clause "New" or "Revised" 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.
grpc-gateway
-
I write HTTP services in Go after 13 years (Mat Ryer, 2024)
it lacks flexibility but i really enjoy grpc-gateway for 99% of my work
https://github.com/grpc-ecosystem/grpc-gateway
-
Create Production-Ready SDKs With gRPC Gateway
gRPC Gateway is a protoc plugin that reads gRPC service definitions and generates a reverse proxy server that translates a RESTful JSON API into gRPC.
-
Ask HN: Rapid Development API-Only One Person Stack – Seeking Performant Tech
I don't have any example that's public atm, but the guide in grpc-gateway is pretty clear/can be followed step by step.
https://github.com/grpc-ecosystem/grpc-gateway
To integrate with Fiber, I used the Fiber Adaptor (also pretty straightforward): https://docs.gofiber.io/api/middleware/adaptor
-
Seeking advice on implementing a tinyurl-like service using Go and gRPC.
I wonder if they would be happy with something like this: https://github.com/grpc-ecosystem/grpc-gateway
- How do I provide bot RPC and REST endpoints?
-
Reasons to use gRPC/Protobuf?
Protobuf is used is massively scaled services like firebase. But you'll still see JSON in streamed realtime services like AWS Kinesis. Hopefully google had a return on investment for creating and using this protocol, but it's not hard to prove that it's far from essential. Out of apparent convenience I use grpc-gateway so I can expose both Protobuf and JSON, but honestly I wouldn't do it again
-
gRPC microservices communication in kubernates
GRPC is an alternative to rest, rest and GRPC both use the http protocol. But you won’t be able to use fetch to call a GRPC endpoint, you should look into setting up a GRPC proxy within the application(hopping you have access to the source code) grpc-gateway. If you don’t have access you’ll have to create a new container that proxies the calls
-
Question about gRPC?
(There is an option called google.api.http, that lets you set up a URL that can be used to make HTTP/1 REST requests, which get translated to gRPC calls if you're using grpc-gateway as a proxy in front of your service. That has nothing to do with the requests that are made by gRPC clients and servers themselves.)
-
Issues with proxying gRPC services to web, and a potential prototype
Have you looked at https://github.com/grpc-ecosystem/grpc-gateway ?
-
Understanding gRPC Concepts, Use Cases & Best Practices
protoc-gen-grpc-gateway — plugin for creating a gRPC REST API gateway. It allows gRPC endpoints as REST API endpoints and performs the translation from JSON to proto. Basically, you define a gRPC service with some custom annotations and it makes those gRPC methods accessible via REST using JSON requests.
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?
examples - A repository to host examples and tutorials for Gin.
bloomrpc - Former GUI client for gRPC services. No longer maintained.
MassTransit - Distributed Application Framework for .NET
grpc-over-webrtc - gRPC over WebRTC
Kreya - Kreya is a GUI client for REST and gRPC with innovative features for environments, authorizations and more.
grpc-web - gRPC for Web Clients
OpenAPI-Specification - The OpenAPI Specification Repository
wrk - Modern HTTP benchmarking tool
grpcui - An interactive web UI for gRPC, along the lines of postman
openapi3 - OpenAPI 3.0 data model
Hey - HTTP load generator, ApacheBench (ab) replacement