easyjson
zap
easyjson | zap | |
---|---|---|
10 | 51 | |
4,350 | 20,981 | |
0.8% | 1.0% | |
2.3 | 8.1 | |
7 days ago | 5 days ago | |
Go | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
easyjson
-
Google's Go may add telemetry reporting that's on by default
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.
- JSON encoder/decoder supporting omitempty on structs
- TinyGo Reflection?
-
Wasm difficulties in Rust, Haskell, and Go
easyjson produced an empty file
-
Using a json lib other than encoding/json
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.
-
What type of software do you write at your workplace?
https://github.com/mailru/easyjson fast JSON (de)serializer which go generates code instead of using reflect at runtime.
-
Whats the fastest JSON unmarshaling package as of right now?
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.
-
Some Go(lang) tips
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.
-
Is there a JSON parsing library that generates specialized code for types?
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, ось приклад тесту який покаже помилку.
zap
- Desvendando o package fmt do Go
-
Building RESTful API with Hexagonal Architecture in Go
The project currently uses slog package from standard library for logging. But switching to a more advanced logger like zap could offer more flexibility and features.
-
Structured Logging with Slog
It's nice to have this in the standard library, but it doesn't solve any existing pain points around structured log metadata and contexts. We use zap [0] and store a zap logger on the request context which allows different parts of the request pipeline to log with things like tenantid, traceId, and correlationId automatically appended. But getting a logger off the context is annoying, leads to inconsistent logging practices, and creates a logger dependency throughout most of our Go code.
[0] https://github.com/uber-go/zap
-
Kubebuilder Tips and Tricks
Kubebuilder, like much of the k8s ecosystem, utilizes zap for logging. Out of the box, the Kubebuilder zap configuration outputs a timestamp for each log, which gets formatted using scientific notation. This makes it difficult for me to read the time of an event just by glancing at it. Personally, I prefer ISO 8601, so let's change it!
-
Go 1.21 Released
What else would you expect from a structured logging package?
To me it absolutely makes sense as the default and standard for 99% of applications, and the API isn't much unlike something like Zap[0] (a popular Go structured logger).
The attributes aren't an "arbitrary" concept, they're a completely normal concept for structured loggers. Groups are maybe less standard, but reasonable nevertheless.
I'm not sure if you're aware that this is specifically a structured logging package. There already is a "simple" logging package[1] in the sodlib, and has been for ages, and isn't particularly fast either to my knowledge. If you want really fast you take a library (which would also make sure to optimize allocations heavily).
[0]: https://pkg.go.dev/go.uber.org/zap
[1]: https://pkg.go.dev/log
- Efficient logging in Go?
-
Why elixir over Golang
And finally for structured logging: https://github.com/uber-go/zap
-
Beginner-friendly API made with Go following hexagonal architecture.
For logging: I recommend using Uber Zap https://github.com/uber-go/zap It will log stack backtraces and makes it super easy to debug errors when deployed. I typically log in the business logic and not below. And log at the entry for failures to start the system. Maybe not necessary for this example, but it’s an essential piece of any API backend.
- slogx - slog package extensions and middlewares
- Why it is so weirdo??
What are some alternatives?
fastjson - Fast JSON parser and validator for Go. No custom structs, no code generation, no reflection
logrus - Structured, pluggable logging for Go.
jsoniter - A high-performance 100% compatible drop-in replacement of "encoding/json"
zerolog - Zero Allocation JSON Logger
go-json - Fast JSON encoder/decoder compatible with encoding/json for Go
slog
gogoprotobuf - [Deprecated] Protocol Buffers for Go with Gadgets
glog - Leveled execution logs for Go
simdjson-go - Golang port of simdjson: parsing gigabytes of JSON per second
go-log - a golang log lib supports level and multi handlers
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
log - Structured logging package for Go.