jvm-serializers
ScalaPB
jvm-serializers | ScalaPB | |
---|---|---|
7 | 3 | |
3,275 | 1,282 | |
- | 0.5% | |
4.4 | 9.0 | |
7 months ago | 6 days ago | |
Java | Scala | |
- | 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.
jvm-serializers
-
Fury: 170x faster than JDK, fast serialization powered by JIT and Zero-copy
Compared with protobuf, fury is 3.2x faster. When comparing with avro, fury is 5.3x faster. Compared with flatbuffers, fury is 4.8x faster. See https://github.com/eishay/jvm-serializers/wiki for detailed benchmark data
-
The state of Java Object Serialization libraries in Q2 2023
First, there's benchmarks here if you haven't seen it: jvm-serializers. Not terribly scientific, but it's something. To make any decision, you really need to benchmark your own object graph and it's important to configure the serializer for your particular usage. Still, it is sort of useful for comparing frameworks. It would be interesting to see how Loial performs there. Ping me if you add it.
-
Up to 100x Faster FastAPI with simdjson and io_uring on Linux 5.19+
It depends. Some binary encodings such as flatbuffer are actually slower than some JSON libraries. There's a wide range of performance even in the JSON libraries themselves. Generally the faster JSON libraries are the ones that work on a predefined schema and so are able to generate code specifically for that JSON.
-
Go standard library: structured, leveled logging
> I'm surprised this is up for debate.
I looked into logging in protobuf when I was seeing if there was a better binary encoding for ring-buffer logging, along the same lines as nanolog:
https://tersesystems.com/blog/2020/11/26/queryable-logging-w...
What I found was that it's typically not the binary encoding vs string encoding that makes a difference. The biggest factors are "is there a predefined schema", "is there a precompiler that will generate code for this schema", and "what is the complexity of the output format". With that in mind, if you are dealing with chaotic semi-structured data, JSON is pretty good, and actually faster than some binary encodings:
https://github.com/eishay/jvm-serializers/wiki/Newer-Results...
-
Scala 3.0 serialization
You could use any of the JVM serialisers which should still work.
ScalaPB
-
Friction-less scala - Tell us what is causing friction in your day-to-day life with Scala
I've had great experience with ScalaPB and even better with fs2-grpc (which builds on top of ScalaPB).
-
Working with polymorphic data models in a REST API
One way I've solved this is to use Protobuf contracts to serialize json with ScalaPB. They have a way implementing oneof that keeps each object individual and separate. Even if you don't decide to use PB, you can take some inspiration from the implementation.
-
Scala 3.0 serialization
You could try out protocol buffers. Not sure how stable it is, but I noticed they have a Scala3 version of their runtime library. (Disclaimer: I have not tried it out myself)
What are some alternatives?
fury-benchmarks - Serialization Benchmarks for fury with other libraries
scodec - Scala combinator library for working with binary data
Apache Avro - Apache Avro is a data serialization system.
ScalaBuff - the scala protocol buffers (protobuf) compiler
zio-json - Fast, secure JSON library with tight ZIO integration.
µPickle - uPickle: a simple, fast, dependency-free JSON & Binary (MessagePack) serialization library for Scala
opentelemetry-specificatio
Pickling
janino - Janino is a super-small, super-fast Java™ compiler.
Scrooge - A Thrift parser/generator
grpc-dotnet - gRPC for .NET
Avro4s - Avro schema generation and serialization / deserialization for Scala