sonic VS fastjson

Since most of the time would be spent decoding json, you could try to cut this time using https://github.com/bytedance/sonic or https://github.com/json-iterator/go, both are drop-in replacements for the stdlib, sonic is faster.

Also worth looking at https://github.com/bytedance/sonic

The article inside does not mention this.

Good morning.I hope this is not the wrong place to post… so let me introduce my first public Golang package. This is a JSON decoder called Sonnet ( https://github.com/sugawarayuuta/sonnet ) that has given faster results (at least in my environment) than Sonic - https://github.com/bytedance/sonic (which is said that it's the fastest) without the help of assembly!

JSON is a very well-known file format. It is used by everyone who does programming. However, it is also not uncommon to find problems with encoding/json and other third-party libraries. for more… (see https://github.com/sugawarayuuta/sonnet#problems-we-had )

I decided to create a new, standard library-compatible decoder that would be both easy to use and fast.

Thanks for reading, feel free to use, help, or ask questions, I look forward to hearing from you. All benchmarks and other information can be found in the link at the top.

Good morning. Let me introduce my first public Go package. This is a JSON decoder called Sonnet ( https://github.com/sugawarayuuta/sonnet ) that has given faster results (at least in my environment) than Sonic (which is said that it's the fastest) without the help of assembly!

I'd say the https://github.com/bytedance/sonic has the fastest encoder due to C and assembly optimization. (Use at your own risk.)

I’ve used fastjson when unmarshalling to Structs is inconvenient. https://github.com/valyala/fastjson

Interesting approach, even though reflection support is supposed to be landing soon, this would be really really useful when using TinyGo. (Fro example, writing web backend serverless functions with Fermyon’s Spin framework for WASM that needs to return JSON). Do you have any benchmarks on how it performs vs stdlib’s encoding/json and/or something like fastjson?

It relies heavily on bytes.IndexOf for which Go provides SIMD optimizations transparently. However, it has some correctness issues when parsing malformed json that might need to be addressed. Generally it is recommended to be used with trusted json documents for internal services and may require further testing before being used to parse arbitrary json documents.

Try fastjson library. It allows you to grab deeply nested json objects without marshalling the entire json.

Como herramientas te recomiendo: FastJson https://github.com/valyala/fastjson : Si necesitas leer jsons Testify https://github.com/stretchr/testify : Para mockear y testear

In Go if I need to extract just a few fields from a large JSON document it's hard to beat https://github.com/valyala/fastjson

Another option is to use what I like to call "Lazy" decoders, like https://github.com/valyala/fastjson which will work with TinyGo, but doesn't have the same type of API as the standard lib (or alternatives) in terms of Marshaling and Unmarshalling. Instead you "Parse" a JSON object, and use Getters to access the types you want.