go_serialization_benchmarks
grpc-web
go_serialization_benchmarks | grpc-web | |
---|---|---|
8 | 33 | |
1,527 | 8,309 | |
- | 0.8% | |
4.4 | 6.4 | |
12 days ago | 16 days ago | |
Go | JavaScript | |
- | 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.
go_serialization_benchmarks
-
Rob Pike: Gobs of data (2011)
Someone made a benchmark of serialization libraries in go [1], and I was surprised to see gobs is one of the slowest ones, specially for decoding. I suspect part of the reason is that the API doesn't not allow reusing decoders [2]. From my explorations it seems like both JSON [3], message-pack [4] and CBOR [5] are better alternatives.
By the way, in Go there are a like a million JSON encoders because a lot of things in the std library are not really coded for maximum performance but more for easy of usage, it seems. Perhaps this is the right balance for certain things (ex: the http library, see [6]).
There are also a bunch of libraries that allow you to modify a JSON file "in place", without having to fully deserialize into structs (ex: GJSON/SJSON [7] [8]). This sounds very convenient and more efficient that fully de/serializing if we just need to change the data a little.
--
1: https://github.com/alecthomas/go_serialization_benchmarks
2: https://github.com/golang/go/issues/29766#issuecomment-45492...
--
3: https://github.com/goccy/go-json
4: https://github.com/vmihailenco/msgpack
5: https://github.com/fxamacker/cbor
--
6: https://github.com/valyala/fasthttp#faq
--
7: https://github.com/tidwall/gjson
8: https://github.com/tidwall/sjson
-
Introducing Tempo: low latency, cross-platform, end-to-end typesafe APIs
The bebop definition specifies fixed-width types inside a struct. The format of structs cannot be changed, but there are efficiency gains by omitting all of the indices and header data. It's useless as the root message, but it's small and fast for a benchmark.
-
mus-go - the fastest Golang serializer today
Hey everyone! Let me introduce you to mus-go - the fastest Golang serializer today. If you look at benchmarks (https://github.com/alecthomas/go_serialization_benchmarks), you can see that it could be almost twice as fast as its closest "competitor":
-
What is the fastest way to encode the arbitrary struct into bytes?
This might be of interest: https://github.com/alecthomas/go_serialization_benchmarks
- 80x improvements in caching by moving from JSON to gob
-
gRPC Is Easy to Misconfigure
The protobuf vs msgpack benchmarks are not too bad. Msgpack performs very decently.
https://github.com/alecthomas/go_serialization_benchmarks
-
Bebop encoding in Go
Maybe submit a PR against https://github.com/alecthomas/go_serialization_benchmarks? That covers a ton of serialization formats already, so adding your library would be cool and avoid wheel reinvention.
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.
What are some alternatives?
bebop - bebop wire format in Go
ngx-grpc - Angular gRPC framework
encoding - Go package containing implementations of efficient encoding, decoding, and validation APIs.
grpc-over-webrtc - gRPC over WebRTC
bebop - 🎷No ceremony, just code. Blazing fast, typesafe binary serialization.
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
msgpack - MessagePack is an extremely efficient object serialization library. It's like JSON, but very fast and small.
buf - The best way of working with Protocol Buffers.
msgp - A Go code generator for MessagePack / msgpack.org[Go]
webrpc - webrpc is a schema-driven approach to writing backend services for modern Web apps and networks
go-codec-bench - Benchmark of go binary and text encodings
evans - Evans: more expressive universal gRPC client