protobuf-ts
connect-go
protobuf-ts | connect-go | |
---|---|---|
13 | 26 | |
951 | 3 | |
- | - | |
6.5 | 0.0 | |
17 days ago | 8 months ago | |
TypeScript | Go | |
Apache License 2.0 | 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.
protobuf-ts
-
tRPC – Move Fast and Break Nothing. End-to-end typesafe APIs made easy
DX for front or back end? The beauty of tRPC is that the types are derived/inferred from the backend runtime code (like, as you type). It would be nigh impossible to do that with grpc(-web) using proto files as the source of truth.
It's possible there's a project out there which could automatically produce proto files from something like zod, json-schema, etc. which could be directly interpreted by TS to provide similar (as you type) DX while still allowing some other language backend to consume the derived proto files (though the DX there would be less than ideal).
If you're just looking for similar TS clients/interfaces for grpc-web then I'd recommend https://github.com/timostamm/protobuf-ts which operates on plain JS objects (no new MyMessage().serialize(), instead the code generator mostly produces TS interfaces for you to work against: const myMessage: MyMessage = pojoConformingToInterface; const binary = MyMessage.toBinary(myMessage);)
-
Error using JWT Authentication using GRPC Web in .net 7; postman works - typescript client does not authorize
https://github.com/timostamm/protobuf-ts (RpcMetaData) https://github.com/timostamm/protobuf-ts/blob/main/MANUAL.md
-
gRPC vs REST: Comparing API Styles in Practice
The second big difference is that we now have auto-generated client and server stubs. For this task, I chose to use buf and the protobuf-ts plugin in order to generate idiomatic Typescript classes and objects. Not only do these classes describe the types we'll use in the server and client, but also includes the actual gRPC implementations used to serialize and send messages back and forth across the wire.
-
Why are gRPC and Node.js so difficult?
I wouldn’t use grpc with web if you can avoid it. If you’re looking for a ts protobuf library I can recommend this one https://github.com/timostamm/protobuf-ts
- GRPC Gateway API Client?
-
Building a real-time bidding system with Socket.io and React Native
https://github.com/timostamm/protobuf-ts looks interesting too.
-
Connect-Web: ergonomic Protobuf & gRPC for browsers
I'd recommend looking into protobuf-ts (Timo from Buf) or protobuf-es (Buf maintained).
-
Rust GRPC
Use a GRPC library for frontend, assuming you want to go with Typescript take a look at https://github.com/timostamm/protobuf-ts Frontend frameworks like Angular/React/Vue don't define what and how to implement backend communication. You can use what you want and how you want it.
-
Connect: A Better gRPC
And there's also this which is by the same author but came before it: https://github.com/timostamm/protobuf-ts
The latter has code-generation for services and has various transport packages for twirp, grpc, and grpc-web.
-
Show HN: Pbkit – Protobuf toolkit written in Deno/TypeScript
This looks very interesting! Anything that can move people away from protobuf.js (which seems to no longer be maintained and depends on prototype values for "default values" meaning that you can't send deserialized protobuf messages to/from web workers) and the "native" JS codegen by Google (which produces code that is both very slow and a awkward to use) is a win in my book.
We're currently using https://github.com/timostamm/protobuf-ts which has been fantastic. It's codegen is dependent on the protoc binary as it is implemented as a protoc plugin, but the code it generates passes the protobuf conformance tests. The generated code also outputs plain objects when deserializing protobuf messages which means it works perfectly when sending stuff to/from web workers. It also has grpc, grpc-web, and twirp clients.
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?
ts-proto - An idiomatic protobuf generator for TypeScript
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
ts-protoc-gen - Protocol Buffers Compiler (protoc) plugin for TypeScript and gRPC-Web.
grpc-gateway - gRPC to JSON proxy generator following the gRPC HTTP spec
grpc-web - gRPC Web implementation for Golang and TypeScript
protobuf-es - Protocol Buffers for ECMAScript. The only JavaScript Protobuf library that is fully-compliant with Protobuf conformance tests.
reflect-metadata - Prototype for a Metadata Reflection API for ECMAScript
twirp - A simple RPC framework with protobuf service definitions
deno-pbf - Deno pbf port of https://github.com/mapbox/pbf
examples-go - An example Go server built with Connect.
drpc - drpc is a lightweight, drop-in replacement for gRPC