bqb
zap
Our great sponsors
bqb | zap | |
---|---|---|
13 | 51 | |
121 | 20,762 | |
- | 1.6% | |
7.1 | 8.1 | |
5 months ago | about 23 hours 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.
bqb
-
Are there any decent ORMs in Golang?
But using a query builder, something like squirrel or (plug) bqb, allows you to actually write SQL (or something close to it) when you need it but also handles the nasty string building bits. Though I agree that ORMs are not always bad, especially for small projects with well-defined scope.
- Examples of Good Go Repos
-
GORM
Plug for bqb as a query builder, but there's also squirrel which works pretty well too.
-
Best packages?
(plug) bqb for very simple query building.
-
ORM vs SQL Builder in Go
Squirrel is great! Let me also plug bqb.
-
Open Source Go Projects for learning go
Plug: BQB (basic query builder) is small, 100% test coverage, and in AwesomeGo. A great starter project.
-
Where to find a virtual or local Go mentor?
I totally understand this. If you do go with a query builder, may I recommend bqb (shameless plug) as it allows you to remain closer to the SQL than some alternatives and doesn't do anything fancy. We stripped out 50% of our query logic with it in our org, which has enabled us to more readily tweak the SQL for performance.
-
Does gorm worth learning?
There's also bqb. We use it in production at our company -- much better than raw SQL. If you couple it with something like scany then you get more of the ORM benefits without the complexity.
-
Any "simple" projects with particularly well-written and/or well-documented code for a beginner to look through?
Another shameless plug: https://github.com/nullism/bqb pretty tiny query builder with 100% test coverage
-
bqb VS Squirrel - a user suggested alternative
2 projects | 9 Sep 2021
zap
-
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.
Oof. We just converted all of our logging to zap[0] to get structured JSON logging for downstream parsing. Wonder how the perf stacks up.
-
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).
-
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 is the common log library which is industry standard that is used in server applications?
What are some alternatives?
logrus - Structured, pluggable logging for Go.
zerolog - Zero Allocation JSON Logger
slog
glog - Leveled execution logs for Go
go-log - a golang log lib supports level and multi handlers
log - Structured logging package for Go.
lumberjack - lumberjack is a log rolling package for Go
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
seelog - Seelog is a native Go logging library that provides flexible asynchronous dispatching, filtering, and formatting.
go-grpc-middleware - Golang gRPC Middlewares: interceptor chaining, auth, logging, retries and more.
log15 - Structured, composable logging for Go
journald - Go implementation of systemd Journal's native API for logging