Our great sponsors
grpc-web | proposal | |
---|---|---|
33 | 5 | |
8,301 | 694 | |
1.2% | 2.2% | |
6.5 | 7.6 | |
11 days ago | 7 days ago | |
JavaScript | ||
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.
grpc-web
-
Ask HN: WebSocket server transforming channel subscriptions to gRPC streams
* Additionally, client can stream data to the backend server (if bidirectional GRPC streams are used). I.e. client sends WebSocket messages, those will be transformed to GRPC messages by WebSocket server and delivered to the application backend.
As a result we have a system which allows to quickly create individual streams by using strict GRPC contract but terminating connections over WebSocket transport. So it works well in web browsers. After that no need to write WebSocket protocol, client implementation, handle WebSocket connection. This all will be solved by a suggested WebSocket server and its client SDKs.
The mechanics is similar to Websocketd (https://github.com/joewalnes/websocketd), but instead of creating OS processes we create GRPC streams. The difference from grpc-web (https://github.com/grpc/grpc-web) is that we provide streaming capabilities but not exposing GRPC contract to the client - just allowing to stream any data as payload (both binary and text) with some wrappers from our client SDKs side for managing subscriptions. I.e. it's not native GRPC streams on the client side - we expose just Connection/Subscription object to stream in both directions. GRPC streams used only for communication between WebSocket server and backend. To mention - grpc-web does not support all kinds of streaming now (https://github.com/grpc/grpc-web#streaming-support) while proposed solution can. This all should provide a cross-platform way to quickly write streaming apps due to client SDKs and language-agnostic nature of GRPC.
I personally see both pros and cons in this scheme (without concentrating on both too much here to keep the question short). I spent some time thinking about this myself, already have some working prototypes – but turned out need more opinions before moving forward with the idea and releasing this, kinda lost in doubts.
My main question - whether this seems interesting for someone here? Do you find this useful and see practical value?
-
Build and Deploy a gRPC-Web App Using Rust Tonic and React
By default, web browsers do not support gRPC, but we will use gRPC-web to make it possible.
-
Lemmy v0.18.0 Release - A reddit alternative written in Rust.
You just have to use a library implementation for JavaScript https://github.com/grpc/grpc-web
-
Full Stack Forays with Go and gRPC
TypeScript support remains an experimental feature of gRPC.
- Seeking Opinion: Choosing Between Gateway and Envoy Proxy for Our Microservices Architecture
-
Introducing Tempo: low latency, cross-platform, end-to-end typesafe APIs
The gRPC-Web protocol supports HTTP/1 and can be used from a browser.
-
gRPC on the client side
-- grpc-web
-
Introduction to gRPC
gRPC is mainly used in server-to-server communication, but it can also be used in client-to-server communication. gRPC-web is a gRPC implementation for web browsers. It is a JavaScript library that allows you to call gRPC services from a web browser. It supports Unary and Streaming Server API calls.
-
gRPC vs REST: Comparing API Styles in Practice
Since we're using Envoy, there's one more neat trick that we can employ. It turns out that Envoy also support gRPC-Web out of the box, a JavaScript client designed to support gRPC communication from the browser! That means that we can send gRPC messages over HTTP/1.1 as base64 encoded strings or as binary protobufs. Messages will be sent through our proxy and on to our backend service. The advantage of this is smaller and more efficient wire communication which should lead to better performance.
-
Understanding gRPC Concepts, Use Cases & Best Practices
protoc-gen-grpc-web — a plugin that allows our front end to communicate with the backend using gRPC calls. A separate blog post on this coming up in the future.
proposal
- gRPC Name Resolution & Load Balancing on Kubernetes: Everything you need to know (and probably a bit more)
- Why HTTP/3 is eating the world
-
eBPF will help solve service mesh by getting rid of sidecars
Not convinced that this a better solution then just implementing most of these features as part of the protocol. Most languages already support grpc load balancing.
https://github.com/grpc/proposal/blob/master/A27-xds-global-...
-
Why gRPC for microservices communication?
The future of gRPC load balancing is proxy less using the xDS APIs of Envoy. More info here. But as of now, there is no straightforward solution since there are no xDS management servers supporting this unless you are on GKE where you can use Traffic Director. Istio has experimental support, and it is said that it works, but it might require some manual configuration. If Go is fine for you, you could also be using go-control-plane, but definitely, the ecosystem around gRPC and xDS does not seem to be mature enough.
- Why Load Balancing Grpc Is Tricky
What are some alternatives?
ngx-grpc - Angular gRPC framework
grpc-over-webrtc - gRPC over WebRTC
kill-zscaler - Kill Zscaler without password or jail Zscaler in a virtual machine
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
HTTP Parser - http request/response parser for c
buf - The best way of working with Protocol Buffers.
membrane_core - The core of the Membrane Framework, advanced multimedia processing framework
webrpc - webrpc is a schema-driven approach to writing backend services for modern Web apps and networks
pixie - Instant Kubernetes-Native Application Observability
evans - Evans: more expressive universal gRPC client
re - Recursive search and replace tool