Apache Fory
Ranked 9 of 9 serialization formats by recommenders
Free open-source serialization framework recommended for object graphs and high throughput. Critics note it relies on internal JDK APIs and question its benchmark data.
Free open-source serialization framework recommended for object graphs and high throughput. Critics note it relies on internal JDK APIs and question its benchmark data.
7 people gave an opinion
- recommend it
- 6
- criticize it
- 1
- approval share
- 86%
Recommended in 4 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 6 people recommend itNeeds 10 or more, not met.
- 6 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 4 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
What people warn about
Each mark is one comment
Relies on internal JDK APIs
“Apache Fury recently fixed this very issue, but it still relies on internal JDK APIs in order to do it's work.”
Comment from 2 Jul 2026 in “JEP 539: Strict Field Initialization in the JVM moved to preview” “Apache Fury recently fixed this very issue, but it still relies on internal JDK APIs”
Comment from 3 Jul 2026 in “JEP 539: Strict Field Initialization in the JVM moved to preview” Benchmark claims questioned
“the data in that blog post doesn't show that”
Comment from 18 Mar 2026 in “Apache Fory C++: 10x faster serialization than protobuf”
Other serialization formats people recommend
The four most recommended other serialization formats, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Protocol Buffers (protobuf) | 77 | 66 | 54% | 10 | 10 yrs3 owners | — |
| Serde | 22 | 16 | 58% | 10 | — | — |
| Cap'n Proto | 20 | 5 | 80% | 7 | — | Approved |
| Protobuf | 19 | 25 | 43% | 8 | — | — |
| Apache ForyThis page | 6 | 1 | 86% | 4 | — | — |
What people said
7 of the 8 comments that mention it, newest first. Each links to the original comment.
“Apache Fory achieved 2.78×–12.12× the throughput of kotlinx.serialization, Moshi with generated adapters, and Jackson Kotlin”
“Apache Fury recently fixed this very issue, but it still relies on internal JDK APIs”
“Apache Fury recently fixed this very issue, but it still relies on internal JDK APIs in order to do it's work.”
“was much slower and much bigger than Kryo 5 with no registration.”
“the data in that blog post doesn't show that”
“With fory first-class object graph serialziation support, you can serialize object graphs without manual *_id link reconstruction”
“The only thing that says is schemeless and is zero copy is Apache Fory”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.