grpc-gateway
connect-go
grpc-gateway | connect-go | |
---|---|---|
30 | 26 | |
17,391 | 3 | |
0.8% | - | |
9.8 | 0.0 | |
2 days ago | 8 months ago | |
Go | Go | |
BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
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.
connect-go
- Code generation for REST inter service communication?
-
Flutter + gRPC for Desktop and Mobile App Development - Good choice?
In my opinion it's a good idea, it's the architecture we use at work, and it works well for us. The main limitation to be aware of is that many PaaS don't support gRPC traffic (because of the proxies used). For example, DigitalOcean App Platform or Heroku if I remember correctly. If the way you want to host your backend is OK with HTTP/2 and gRPC traffic, then it's not a limitation. One way around this limitation is to use the gRPC-Web protocol, or the Connect protocol (https://connect.build/). Unfortunately, Dart's gRPC client does not support the gRPC-Web protocol outside the web platform. So for a mobile application, it's not usable at the moment. (If this PR were accepted, it would solve the issue: https://github.com/grpc/grpc-dart/pull/557.) As for Connect, no client is currently offered by Buf for Dart. Don't hesitate if you want to know more. That said, I'd advise you to use the Connect implementation for Go to implement your backend. Connect will enable your server to speak all three protocols (gRPC, gRPC-Web and Connect), which is very useful in the long term. What's more, the code is cleaner, and you benefit from official support for observability with OpenTelemetry. If you don't know Buf (the creators of Connect),I suggest you visit their website: https://buf.build/. :-) Good luck!
- How do I provide bot RPC and REST endpoints?
-
Building a modern gRPC-powered microservice using Node.js, Typescript, and Connect
As mentioned in the intro, we are going to use Buf and Connect as our tools. We’ll start by installing the dependencies.
- Ask HN: Is it possible to compile TypeScript to Golang?
-
gRPC + Envoy + grpc-web = scalable multiplexed streaming?
Its annoying, because the rest of Connect (https://connect.build/) looks really really cool. But its no good for me in a complex app if I can't have multiple streams from the server :/
-
Issues with proxying gRPC services to web, and a potential prototype
Consider checking out https://connect.build from https://buf.build. Supports a simpler protocol than grpc-web. Includes a js/ts client for frontend. Then you don’t necessarily need a rest layer, but could leverage the proxy your building.
-
Best Web Sever Framework?
Twirp (though I'd move to https://connect.build for my next project) to do JSON based RPC using protobufs.
-
GRPC Gateway API Client?
my backend is go via https://github.com/bufbuild/connect-go , it's stable and all open source. just try and test it for your purpose. my project run all in 300 server more....
- Connect – A Better gRPC
What are some alternatives?
examples - A repository to host examples and tutorials for Gin.
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
MassTransit - Distributed Application Framework for .NET
protobuf-es - Protocol Buffers for ECMAScript. The only JavaScript Protobuf library that is fully-compliant with Protobuf conformance tests.
Kreya - Kreya is a GUI client for REST and gRPC with innovative features for environments, authorizations and more.
twirp - A simple RPC framework with protobuf service definitions
OpenAPI-Specification - The OpenAPI Specification Repository
examples-go - An example Go server built with Connect.
grpc-web - gRPC for Web Clients
drpc - drpc is a lightweight, drop-in replacement for gRPC
openapi3 - OpenAPI 3.0 data model
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)