connect-go
protobuf
connect-go | protobuf | |
---|---|---|
26 | 18 | |
3 | 9,657 | |
- | 0.6% | |
0.0 | 4.6 | |
9 months ago | 14 days ago | |
Go | JavaScript | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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
protobuf
- Eval("quire".replace(/^/,"re"))(moduleName)
-
How we reverse-engineered Google Maps pagination
Google Maps URLs contain the pb parameter contains string-encoded Protobuf. The format is the same as for the data parameter in the browser URL on Google Maps. It contains !-separated values. There are several answers on StackOverflow, gists on GitHub, some blog posts about decoding, and even a kinda official guide on reverse engineering protobuf, but none of this touches pagination.
-
Add extra stuff to a “standard” encoding? Sure, why not
Seems like protoduf.js has the exact same methods as Google’s implementations with the same names (encode/decode to not prepend with length, encodeDelimited/decodeDelimited for prepending length). It is hard for me to say they’re adding to the standard when they’re just replicating Google’s libraries.
https://github.com/protobufjs/protobuf.js#toolset
-
Question about compressing JSON in multiplayer position updates
If it really is a problem, then another option is to use Protobus or Message Pack for serializing (maybe into base64?).
-
Looking for ideas on how to implement serialization and deserialization between C++ and Javascript
I use protocol buffers. protobufjs translates into json.
-
GRPC Gateway API Client?
I have tried GRPC gateway generation tools: - PBJS: https://github.com/protobufjs/protobuf.js/
- Protobuf-ES: The Protocol Buffers TypeScript/JavaScript runtime we all deserve
- Did I understand the basic concept of website development with Node Js correctly?
- how can i use protobuf with sveltekit, please?
-
is there any startup or famous web app using grpc/grpc-web for their frontend
We use https://github.com/improbable-eng/grpc-web for the server part with https://github.com/protobufjs/protobuf.js on the frontend.
What are some alternatives?
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
snappy - DEPRECATED - please use https://github.com/Brooooooklyn/snappy. Nodejs bindings to Google's Snappy compression library
grpc-gateway - gRPC to JSON proxy generator following the gRPC HTTP spec
pbf - A low-level, lightweight protocol buffers implementation in JavaScript.
protobuf-es - Protocol Buffers for ECMAScript. The only JavaScript Protobuf library that is fully-compliant with Protobuf conformance tests.
compactr - Schema based serialization made easy
twirp - A simple RPC framework with protobuf service definitions
Vicis - Presentation and transformation layer for data output in RESTful APIs.
examples-go - An example Go server built with Connect.
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
drpc - drpc is a lightweight, drop-in replacement for gRPC
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library