grpc-web | gqless | |
---|---|---|
33 | 10 | |
8,309 | 3,672 | |
0.8% | 0.0% | |
6.4 | 0.0 | |
16 days ago | about 2 years ago | |
JavaScript | TypeScript | |
Apache License 2.0 | GNU General Public License v3.0 only |
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.
gqless
-
graphql-code-generator VS gqless - a user suggested alternative
2 projects | 2 Jun 2023
-
GraphQL code generator, how to make query without existing document?
Maybe GQLess is for you? It's a client that magically creates a query from they way you use objects in your react components.
-
Instant realtime GraphQL with built-in authorization for SQL Server
Yes! We announced experimental support earlier and here's the new spec we're implementing that will support all databases and remote schemas too.
https://github.com/hasura/graphql-engine/issues/6991
General support for inherited roles is one of the things I'm most excited about because it makes a bunch of hard things around reusing and composition so easy.
This improvement plays really well along with things like "role-based schemas" so that GraphQL clients have access to just the exact GraphQL schema they should be able to access - which is in turn composed by putting multiple scopes together into one role.
Also interesting is how well this could play with other innovations on the GraphQL client ecosystem like gqless[1] and graphql-zeus[2] because now there's a typesafe and secure SDK for really smooth developer experience on the client side.
[1]: https://github.com/gqless/gqless
- GQless: A GraphQL client built for rapid iteration
-
Hacker News top posts: Jun 2, 2021
GQless: A GraphQL client built for rapid iteration\ (6 comments)
- GQless – a GraphQL client built for rapid iteration
-
Ask HN: What novel tools are you using to write web sites/apps?
Cannot recommend gqless highly enough for making graphql actually fun to use and closer to something like meteor/firebase syntax[0].
And I’ll self-promote, but I’ve been working on what I consider to be a “next generation” style system for React that solves my biggest issue with it currently: being able to performantly write styles in a nice syntax that optimize for both web and native. Called SnackUI, though it’s still in beta[1].
[0] https://gqless.com
[1] https://github.com/snackui/snackui
-
REST vs. gRPC vs. GraphQL
On the GraphQL side you can use gqless[0] (or the improved fork I helped sponsor, here[1]). It's by far the best DX I've had for any data fetching library: fully typed calls, no strings at all, no duplication of code or weird importing, no compiler, and it resolves the entire tree and creates a single fetch call.
[0] https://github.com/gqless/gqless
[1] https://github.com/PabloSzx/new_gqless
What are some alternatives?
ngx-grpc - Angular gRPC framework
graphql-zeus - GraphQL client and GraphQL code generator with GraphQL autocomplete library generation ⚡⚡⚡ for browser,nodejs and react native ( apollo compatible )
grpc-over-webrtc - gRPC over WebRTC
htmx - </> htmx - high power tools for HTML
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
vue-gqty - Experimental Vue composable for gqty
buf - The best way of working with Protocol Buffers.
wundergraph-demo - This Repository demonstrates how to combine 7 APIs (4 Apollo Federation SubGraphs, 1 REST, 1 standalone GraphQL, 1 Mock) into one unified GraphQL API which is then securely exposed as a JSON API to a NextJS Frontend.
webrpc - webrpc is a schema-driven approach to writing backend services for modern Web apps and networks
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
evans - Evans: more expressive universal gRPC client
purescript-flame - Fast & simple framework for building web applications