Backend Development 7 min read

FastJson: What It Is, Performance Comparison, Popularity Issues, and Why to Abandon It

The article introduces Alibaba's FastJson library, presents a benchmark showing it is only modestly faster than Jackson, discusses its limited popularity and numerous unresolved issues, and concludes that projects should prefer Jackson and gradually drop FastJson in favor of more reliable JSON parsers.

Architect's Tech Stack
Architect's Tech Stack
Architect's Tech Stack
FastJson: What It Is, Performance Comparison, Popularity Issues, and Why to Abandon It

1. What is FastJson

FastJson is an open‑source JSON parsing library from Alibaba that can parse JSON strings, serialize Java beans to JSON, and deserialize JSON back to Java beans.

It is a commonly used library among Java developers, and its main selling point is speed.

2. Is it really fast?

Without research there is no right to speak; a simple benchmark comparing FastJson with the widely used Jackson and Google’s Gson was performed on JDK 8, AMD 3700X, 3200 MHz RAM, testing both simple and complex objects for 10 million conversions.

The results show FastJson is indeed the fastest, about 20 % faster than Jackson, while Gson is the slowest by a large margin. However, the test does not cover memory usage or large documents, and speed alone should not be the sole criterion for library selection.

In modern applications even the slowest Gson meets requirements; other optimizations such as I/O tuning and parallel processing are more effective than choosing a marginally faster library.

3. FastJson is not that popular

FastJson’s Maven usage is far lower than Jackson and Gson, and it lacks the extensive ecosystem of the Jackson family.

Some Chinese forums claim FastJson is a low‑quality domestic library, though the author’s own projects have used it without bugs.

There are over 1300 unresolved issues on its GitHub repository, some of which are demonstrated in the following screenshots.

Test code (shown as an image) was used, and after updating to the latest version the same problems persisted, revealing serious logical errors in the library’s handling of certain date‑time formats.

Incorrect formats such as “1970‑01‑01 00:00:00.000000000.000000000” are parsed successfully, while correct formats like “1970‑01‑01 00:00:00” fail.

Combined with community feedback, the author concludes FastJson is not as excellent as claimed.

4. Abandon FastJson

In the author’s projects, Jackson is used as the JSON parser to keep dependencies minimal, while some colleagues still use Gson or FastJson without strict guidelines.

Jackson’s popularity has intrinsic reasons, and future projects will favor Jackson and gradually phase out FastJson.

——

Recent high demand for interview questions led the author to compile a second‑edition PDF titled “Internet Big‑Company Interview Questions”, containing 92 PDFs and over 3,600 pages covering Java, JVM, concurrency, Spring, MyBatis, Kafka, Linux, and many other technologies.

Readers can obtain the PDF by scanning the QR code below or replying with the keyword “面试题”.

Scanning the QR code will allow immediate download of the collection.

Yes, scan the code to download – no need to reply with a keyword.

BackendJavaperformancefastjsonGsonJacksonJSON parsing
Architect's Tech Stack
Written by

Architect's Tech Stack

Java backend, microservices, distributed systems, containerized programming, and more.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.