connect-es
protoc-gen-validate
Our great sponsors
connect-es | protoc-gen-validate | |
---|---|---|
13 | 6 | |
1,202 | 3,642 | |
3.4% | 1.4% | |
9.2 | 8.0 | |
6 days ago | 6 days 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.
connect-es
-
I Reviewed 1,000s of Opinions on gRPC
> However, it's important to note that browser support wasn't a primary focus in gRPC's design. This oversight necessitates an additional component, grpc-web, for browser accessibility. Furthermore, external services often have specific needs like caching and load balancing, which are not directly catered to by gRPC. Adopting gRPC for external services might require bespoke solutions to support these features.
The article should mention the Connect protocol for web-based Protobuf messaging:
https://connectrpc.com/
-
Creating the Local First Stack
We can solve this with a service! Now there are many ways I could have started, but I decided to test out gRPC along the way. This was a mistake. I hoped for the best, but gRPC ended up not being a good choice for the web client. Why? you ask. The gRPC protocol works with all the bells and whistles of http when used server to server, but web clients are not as great. The Javascript client is dependent on http 2.0, and it requires a proxy like Envoy to work with a browser. What's more, I didn't love the structure of the generated web client. So through the process of working on this 'local first stack' I actually got sucked in to a big rabbit hole in making the rpc system work. I ended up going with Connect which is a tool that can create a service from a protobuf service definition, that also talks a simple http 1.1 protocol. What ultimately sold me on this solution as the best is that it also came with a very nice to use web client generation, and even plugs in to my favorite react http helper useQuery.
-
Leveraging Temporal for resilient remote procedure calls (RPC)
Our stack at Escape is written in multiple languages because each team has specific needs. We use TypeScript for its vibrant ecosystem, Python for cybersecurity research and Go for performance-sensitive tasks. To orchestrate cross-language task orchestration, we first developed a simple request-response protocol over HTTP, but it wasn't sustainable as the Escape codebase grew rapidly. We evaluated several technologies to replace our homegrown protocol, and two emerged as the most promising options: Connect and Temporal. The title gives it away, but the reason is far from obvious
- Connect RPC – A Better gRPC
-
Building a modern gRPC-powered microservice using Node.js, Typescript, and Connect
protobuf messages we’ll configure (@bufbuild/connect-es)
-
TypeScript type safety with GO
try https://github.com/bufbuild/connect-web
-
Ask HN: Why isn't JSON-RPC more widely adopted?
As for better gRPC-web, you might want to look into connect-web https://github.com/bufbuild/connect-web
- When to use gRPC vs GraphQL
-
Protobuf-ES: The Protocol Buffers TypeScript/JavaScript runtime we all deserve
They already have! Connect (https://github.com/bufbuild/connect-web) is what you're looking for, as it's grpc-web compatible.
-
Connect-Web: It's time for Protobuf/gRPC to be your first choice in the browser
Ye, fwiw there is an example code size comparison here:
https://github.com/bufbuild/connect-web/blob/main/packages/c...
I'm sure someone will chime in on the implementation details, but hopefully others can give it a try with their projects!
protoc-gen-validate
- Protobuf Schema Validation
-
Protobuf-ES: The Protocol Buffers TypeScript/JavaScript runtime we all deserve
My understanding is that the powers that be within Google have decided that validating messages is outside the scope of schemas and serialization. protoc-gen-validate provides a portable way to perform validation: https://github.com/bufbuild/protoc-gen-validate
The problem with required fields is it kicks the can down the road when you want to deprecate a field. Keeping everything optional is much, much better for everyone in the long run.
-
Why isn't gRPC used more for browser to api transport over REST / graphql?
I built a (go) very rough draft to support 3.1 + a json pointer pkg to support a refactor that was in progress before I bailed on the idea. The amount of effort to get a conventional API was dwarfing that of grpc, especially with protoc-gen-validate.
- Protoc-Gen-Validate (PGV)
-
is there any package to generate validation code for struct instead of using reflect (tags)?
Yes, I am currently using this. I prefer something like this https://github.com/envoyproxy/protoc-gen-validate
-
sneak peak: code generation extensions to prost (protobuf code generator)
We've been using Rust with protobuf, but had to write lots of conversions from protobuf struct to actual DTO, since prost generates Options for nested types, and does not really support custom types. So I extended prost with the options that we needed. I might aim to also support protoc-gen-validate.
What are some alternatives?
protobuf-es - Protocol Buffers for ECMAScript. The only JavaScript Protobuf library that is fully-compliant with Protobuf conformance tests.
buf - The best way of working with Protocol Buffers.
grpc-web - gRPC for Web Clients
prototool - Your Swiss Army Knife for Protocol Buffers
ts-proto - An idiomatic protobuf generator for TypeScript
prost - PROST! a Protocol Buffers implementation for the Rust Language
ozzo-validation - An idiomatic Go (golang) validation package. Supports configurable and extensible validation rules (validators) using normal language constructs instead of error-prone struct tags.
fastify-autoroutes - fastest way to map directories to URLs in fastify
grpc-web - gRPC Web implementation for Golang and TypeScript
connect-go - Moved to https://github.com/connectrpc/connect-go
protolock - Protocol Buffer companion tool. Track your .proto files and prevent changes to messages and services which impact API compatibility.