Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Jvm-serializers Alternatives
Similar projects and alternatives to jvm-serializers
-
-
opentelemetry-specification
Specifications for OpenTelemetry
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
self-hosted
Sentry, feature-complete and packaged up for low-volume deployments and proofs-of-concept
-
-
-
MessagePack for C# (.NET, .NET Core, Unity, Xamarin)
Extremely Fast MessagePack Serializer for C#(.NET, .NET Core, Unity, Xamarin). / msgpack.org[C#]
-
fury-benchmarks
Serialization Benchmarks for fury with other libraries
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
incubator-fury
A blazingly fast multi-language serialization framework powered by JIT and zero-copy.
-
-
-
opentelemetry-go-contrib
Collection of extensions for OpenTelemetry-Go.
-
-
-
MemoryPack
Zero encoding extreme performance binary serializer for C# and Unity.
-
-
-
java-json-benchmark
Performance testing of serialization and deserialization of Java JSON libraries
-
honeycomb-opentelemetry-go
Honeycomb's OpenTelemetry Go SDK distribution
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
jvm-serializers reviews and mentions
-
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
Fury is also the fastest java serialization in the https://github.com/eishay/jvm-serializers/wiki
There are too many java serialization libraries, I compared fury with jdk/kryo/fst/protostuff/protobuf/flatbuffers/thrift/msgpack/canproto/acro/jackson/json. Fury are fastest too. See https://github.com/eishay/jvm-serializers/wiki to detailed benchmark results.
It's a hard choice to select one for the title, so I use JDK for it, which may be not a good choice.
BTW, fury support jit serialization for jdk17 record, which is super fast compared to other serialization frameworks such as kryo
-
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.
-
A note from our sponsor - InfluxDB
www.influxdata.com | 17 Apr 2024
Stats
The primary programming language of jvm-serializers is Java.
Popular Comparisons
- jvm-serializers VS fury-benchmarks
- jvm-serializers VS Apache Avro
- jvm-serializers VS zio-json
- jvm-serializers VS grpc-dotnet
- jvm-serializers VS janino
- jvm-serializers VS opentelemetry-specificatio
- jvm-serializers VS honeycomb-opentelemetry-go
- jvm-serializers VS skywalking
- jvm-serializers VS MemoryPack
- jvm-serializers VS ScalaPB