Squirrel
zap
Our great sponsors
Squirrel | zap | |
---|---|---|
52 | 51 | |
6,505 | 20,947 | |
1.7% | 1.7% | |
2.8 | 8.1 | |
about 2 months ago | 1 day ago | |
Go | Go | |
GNU General Public License v3.0 or later | 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.
Squirrel
-
Building RESTful API with Hexagonal Architecture in Go
It uses Gin as the HTTP framework and PostgreSQL as the database with pgx as the driver and Squirrel as the query builder. It also utilizes Redis as the caching layer with go-redis as the client.
-
Working with postgres in GO.
I would add Squirrel to PGX https://github.com/Masterminds/squirrel
-
how to avoid writing dreadful SQL statements
I have written about this before, and my thoughts always settle on using a query builder. I've built a simple one, which works for what I need, but there are more feature complete ones out there such as squirrel. I've also written about how you can implement a simple CRUD library for database interactions using generics and query building to have that nice middle-ground between an ORM and query building.
-
How do I enable filters for the user without writing redundant SQL?
Now for the dynamic queries you have to be really careful to prevent SQL injections, there are bunch of different ways to do it but I typically recommend using a package such as squirrel that lets you do this easily, you use it to generate the plain SQL you need (and then use sqlx, database/sql, pgx or whatever you prefer) or use it directly querying the database directly.
-
Best sqlc alternative for dynamic queries?
Here are 2 options for you * https://github.com/huandu/go-sqlbuilder * https://github.com/Masterminds/squirrel
-
Golang RESTAPI boilerplate repository
https://www.reddit.com/r/golang/comments/vq98ud/what_sql_library_are_you_using/ Jet havn't used but is one that looks promising! Otherwise I'm one of the purests, db/sql and https://github.com/Masterminds/squirrel
-
Why is Raw SQL preferred over ORM in go?
I think he means an sql builder like squirrel. This allows dynamic queries, but more important you can reuse function that build a where clause so you can get a count and query with that.
-
Does Go, has something similar to Laravel eloquent (ORM) ?
I'd rather suggest the use of tools more aligned with the core concepts of the language such as sqlx, which is an extension of the database/sql standard library. It allows you to use models/structs to map your tables but you have more control over the SQL statements you use to perform queries and the like. You can combine sqlx with Squirrel to build queries from composable parts.
-
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.
-
GORM
Plug for bqb as a query builder, but there's also squirrel which works pretty well too.
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?
goqu - SQL builder and query library for golang
logrus - Structured, pluggable logging for Go.
sqlx - general purpose extensions to golang's database/sql
zerolog - Zero Allocation JSON Logger
GORM - The fantastic ORM library for Golang, aims to be developer friendly
slog
InfluxDB - Scalable datastore for metrics, events, and real-time analytics
glog - Leveled execution logs for Go
sqlc - Generate type-safe code from SQL
go-log - a golang log lib supports level and multi handlers
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
log - Structured logging package for Go.