chaokunyang

6 ms·

31.
by chaokunyang 1y ago
DOP is very interesting, I like this idea too — most DOP approaches are implemented via an IDL, which is another valid direction. I plan to support that in Fory. I want to give users the freedom to choose the model that works best for them.
32.
by chaokunyang 1y ago
Binary XML encoding (like W3C EXI) is useful in some contexts, but it’s generally not as efficient as modern binary serialization formats. It also can’t naturally express shared or circular reference semantics, which are important for compl
33.
by chaokunyang 1y ago
Apache Arrow is more of a memory format than a general‑purpose data serialization system. It’s great for in‑memory analytics and GPU‑friendly columnar storage. Apache Fory, on the other hand, has its own wire‑stream format designed for send
34.
by chaokunyang 1y ago
In our Java benchmarks, Fory is actually faster than FlatBuffers — you can try it yourself here: https://github.com/apache/fory/blob/main/java/benchmark/src/... We haven’t tested FlatBuffe
35.
by chaokunyang 1y ago
JS support is still experimental, I have not publish it to npm
36.
by chaokunyang 1y ago
The https://github.com/apache/fory/blob/main/AGENTS.md is a very detailed document only for AI coding, but an excelent reference for development. But you are right, it may introduce concerns, let me remo
37.
by chaokunyang 1y ago
should be ok now
38.
by chaokunyang 1y ago
Fory also compress integers using varint or zigzag encoding. The size are basically same: | data type | data size | fory | protobuf | | --------------- | --------- | ------- | -------- | | simple-struct | small | 21 | 19
39.
by chaokunyang 1y ago
I get your concern — for one or two languages, skipping an IDL can work well and keeps things simple. But once you’re dealing with three or more languages, I agree an IDL becomes valuable as a single source of truth. That’s work we’ve start
40.
by chaokunyang 1y ago
This is our first release for Fory Rust. The Java and Python bindings has been used widely. You can see from https://fory.apache.org/user
41.
by chaokunyang 1y ago
You don’t need to hand‑write serializer code. In typed languages you just define your class or struct as usual; in dynamic languages you can use type hints. When running in compatible mode, Fory automatically derives a compact schema from t
42.
by chaokunyang 1y ago
Probably not for everyone. The current limit of 4096 types could be expanded if there’s a real need — it’s not a hard technical barrier. I’m curious though: what’s an example scenario you’ve seen that requires so many distinct types? I have
43.
by chaokunyang 1y ago
That’s a fair point — with more languages in the mix, having a formal schema can definitely help prevent drift. The way I think about it is: • Single‑language projects often work best without an IDL — it keeps things simple and avoids extra
44.
by chaokunyang 1y ago
No, it's not needed. We plan to remove Google Guava from the Fory Java dependency. Our philosophy is that the core should have as few dependencies as possible for maintainability and minimal footprint.
45.
by chaokunyang 1y ago
Apache Fory is also a drop-in replacement for pickle/cloudpickle, you can use it to serialize code object such as local function/Classes too. https://github.com/apache/fory/tree/main/python#seri
46.
Show HN: Apache Fory Rust – 10-20x faster serialization than JSON/Protobuf(fory.apache.org)
67 points by chaokunyang 1y ago|59 comments
47.
Apache Fory Rust – Polyglot serialization with trait objects and circular refs(fory.apache.org)
5 points by chaokunyang 1y ago|1 comments
48.
by chaokunyang 1y ago
Apache Fory is a serialization framework that works across languages without schema files. We just released the Rust implementation (v0.13) with some features we haven't seen elsewhere: 1. Serialize Box/Rc/Arc<dyn Trai
49.
Apache Fory Graduates to Top-Level Apache Project(fory.apache.org)
3 points by chaokunyang 1y ago|1 comments
50.
by chaokunyang 1y ago
Apache Fory is a blazingly-fast multi-language serialization framework powered by JIT (just-in-time compilation) and zero-copy, providing up to 170x performance and ultimate ease of use.
51.
Apache Fory Serialization Framework 0.11.2 Released(github.com)
2 points by chaokunyang 1y ago|0 comments
52.
Apache Fory Serialization Framework 0.11.0 Released(github.com)
2 points by chaokunyang 1y ago|0 comments
53.
Serialization Framework Announcement – Apache Fury Is Now Apache Fory(fory.apache.org)
1 points by chaokunyang 1y ago|1 comments
54.
by chaokunyang 1y ago
The Apache Fury team is now officially announcing that Apache Fury has been renamed to Apache Fory, effective immediately. This transition impacts all project components including code repositories, package names, documentation, and communi
55.
2X compression ratio: Chunk based dynamic map serialization(github.com)
1 points by chaokunyang 2y ago|1 comments
56.
by chaokunyang 2y ago
Available since https://github.com/apache/fury/releases/tag/v0.10.0
57.
by chaokunyang 2y ago
See https://github.com/apache/fury for details about Apache Fury serialization framework
58.
Show HN: Quarkus Fury – Fast native serialization by codegen built on Fury(docs.quarkiverse.io)
1 points by chaokunyang 2y ago|1 comments
59.
Apache Fury: reflection free and 50x faster serialization framework for graalvm(github.com)
1 points by chaokunyang 2y ago|1 comments
60.
by chaokunyang 2y ago
Apache Fury is a blazingly-fast serialization framework for jdk. Apache Fury use automatic codegen for object graph serialization at graalvm native image build time. It eliminate all reflection and introspection at runtime. In this way and

More ›