grpc-web

Improbable's grpc-web [1] works pretty well. I have been using it along with their new websocket transport for about two months and as an RPC layer its great. However I do miss being able to inspect the traffic in devtools, and the TS sdk is still not ESM friendly and requires jumping through hoops to get working with vite. So we ended up bundling it separately through esbuild (along with other google protobuf deps etc.) to a large single file ESM module that other projects can easily consume. Buf seems to be a solution that handles all of this better. Very excited to try this out. [1] https://github.com/improbable-eng/grpc-web

If you're talking about: https://pkg.go.dev/github.com/improbable-eng/grpc-web/go/grp... Then it looks good to me, as long as it's HTTP/1.1 or WebSockets, it will should work everywhere. Is this something you can add soon? We're in a refactoring stage and would love SpiceDB to be a part of it all. (I also created an issue in the repo)

Did you try https://github.com/improbable-eng/grpc-web ?

I heard it's better now but when I was trying to do grpc I couldn't get this to build: https://github.com/improbable-eng/grpc-web/tree/master/go/gr... Basically there was dependency that changed, and it caused it to not build. The maintainer was just pointing fingers at google. I had no idea what to do, but it just scared the crap out of me.

My team has been using gRPC + Improbable's grpc-web [0] + Typescript for a green field project and it has been amazing. - Typing all the way to the frontend. - gRPC/protobuf forces you to describe your interfaces and are self-documenting. - gRPC semantics like error codes and deadlines (if you propagate them through your stack, they're particularly useful - for instance, we cancel database transactions across service boundaries if a request times out). - Performance is great (but we're far from seeing bottlenecks with JSON, it's not the reason we choose gRPC). - We use grpc-gateway which auto-generates a REST proxy for our customers. We sometimes use it for interactive debugging. [1] - Rather than importing database models for our management tools and one-off scripts, using the API is so frictionless that we even use it inside our backend

Can someone describe why gRPC-Web needs a proxy? I recently had trouble deciding between the official gRPC-Web and Improbable's gRPC-Web[1]. In the end I decided on Improbable's, because it seemed to not require a proxy. In practice, it's working very nicely. Yet, I'm still not clear on what exactly the Proxy serves to do, in either case. If a browser supports HTTP 2, why is a proxy needed? [1]: https://github.com/improbable-eng/grpc-web

I am using improbable-webs grpc-web[0] right now and it works very well once some kinks were worked out. Only problem has been lack of client-side streaming. Additionally, I use grpcc[1] to test calls locally and that has worked well. I originally tried using some GUI's that looked promising but couldnt get them to work. This is good enough and less work than writing a quick client in python. [0]: https://github.com/improbable-eng/grpc-web [1]: https://github.com/njpatel/grpcc

> Next up, browser support? Please! There is a working TypeScript client implementation [0] of gRPC-Web [1], which relies on a custom proxy for converting gRPC to gRPC-Web [2]. Would be nice to bring that proxy functionality into Nginx. [0] https://github.com/improbable-eng/grpc-web/tree/master/ts [1] https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-WEB.md [2] https://github.com/improbable-eng/grpc-web/tree/master/go/gr...

It is possible to use gRPC directly from JavaScript using the gRPC-Web [1] project by Improbable. More accurately, it uses TypeScript, which is generated from the proto file in a similar way to other languages. You still need a proxy to transform requests from HTTP/1.1 to HTTP/2.0. I've actually only used the gRPC JSON gateway mentioned in the other replies so I'm not sure how it compares, but it looks interesting. [1] https://github.com/improbable-eng/grpc-web

There has recently been a lot of work for native grpc client in the browser. It’s not fully there yet but is looking real promising! https://github.com/improbable-eng/grpc-web

HTTP 1.1 + json support for twirp opens up a lot of doors too. It's easy for the browser to natively hit a twirp service without the need for large packages such as https://github.com/improbable-eng/grpc-web.

This seemed very promising, protobuffers to automated typescript over gRPC. https://github.com/improbable-eng/grpc-web

routing/binding/cors: chi / echo database: sqlx, upper, sqlboiler log: zap, zerolog dependency management: dep config: viper cli: cobra lint: gometalinter Trying https://github.com/improbable-eng/grpc-web and http://rest-layer.io

I am converting my proto to typescript with https://github.com/improbable-eng/grpc-web and until recently also used their go server library. That meant my grpc servers were listening on 2 ports, gRPC and gRPC-web. I since replaced the gRPC-web part with envoy. Works fine together with the gRPC-web typescript. The gist should give you an idea how to set up a small example. https://gist.github.com/codesuki/f0514368a30b483058007f5fe38...

We've been using grpc-web from Improbable successfully for internal services. I'm working on a more production scale application soon that I'm planning on leveraging grpc-web for. The biggest missing feature is client side streaming support which is hamstrung the new wgfetch/streams API, but I feel confident in finding solutions for situations that generally require client side streaming. https://github.com/improbable-eng/grpc-web