easyjson VS jsonparser

Compile time means you catch issues at... well compile time. It also means that the code is optimized. You can look at the performance different between encoding/json and easyjson for why you may desire that.

easyjson produced an empty file

There is https://github.com/mailru/easyjson out there if you are absolutely sure that serialization is the bottleneck. Otherwise I'd go for stdlib.

https://github.com/mailru/easyjson fast JSON (de)serializer which go generates code instead of using reflect at runtime.

If you know the schema of the JSON ahead of time and you need to parse the whole object, I would recommend https://github.com/mailru/easyjson as that will likely give you the fastest result. This works in almost all use cases, and easy to use features such as string interning can save you a lot of time on memory allocation if you parse a lot of JSON objects with identical values.

What to use Easyjson is about the top of the pack and it's straightforward. The downside of efficient tools is that they use code generation to create the code required to turn your structs into json to minimise allocations. This is a manual build step which is annoying. Interestingly json-iterator also uses reflection but it's significantly faster. I suspect black magic.

I'm looking for something similar to https://github.com/mailru/easyjson where one can generate a concrete JSON parser for some types.

Бібліотека easyjson теж для серіалізації працює через додатковий код замість використання рефлексії. Але після внесення в easyjson одної з оптимізацій, час від часу почали отримувати зламаний JSON, ось приклад тесту який покаже помилку.

In this article, I will introduce you to a new package called astjson that I have been working on for the last couple of weeks. It is a Go package that allows you to transform and merge JSON objects with unmatched speed. It is based on the jsonparser package by buger aka Leonid Bugaev and extends it with the ability to transform and merge JSON objects at unparalleled performance.

Use this to extract the data value, and handle/unmarshal it accordingly.

jsonparser can decode, but can't encode

Best I've found is this: https://github.com/buger/jsonparser

I was actually just trying to get it into a []byte to use this package which claims it works well for unknown data structures.

`jj` is a little tool I wrote that uses https://github.com/buger/jsonparser

If you don't know the schema or you only need to access one or two fields in a much larger JSON object, I would recommend https://github.com/buger/jsonparser as it provides an easy API to access specific values without fully unmarshaling. This is an unusual use case though, 9 times out of 10 I would tend to use easyjson.

Reading and navigating arbitrary JSON: I've used https://github.com/tidwall/gjson, many others like https://github.com/buger/jsonparser are also out there.