logrus
Structured, pluggable logging for Go. (by sirupsen)
pgx
PostgreSQL driver and toolkit for Go (by jackc)
Our great sponsors
logrus | pgx | |
---|---|---|
32 | 71 | |
24,012 | 9,414 | |
- | - | |
3.0 | 9.2 | |
about 1 month ago | 7 days ago | |
Go | Go | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
logrus
Posts with mentions or reviews of logrus.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-02.
-
Authentication system using Golang and Sveltekit - Initialization and setup
It's some sort of logging system well explained by Alex Edwards in Let’s Go Further. As stated, we could have used logrus or any other popular logging system in Go.
-
Renaming public Go modules
Option 2, please. You may not have been around for the logrus debacle, but it was a giant pain.
- What is the common log library which is industry standard that is used in server applications?
-
Observing AWS Lambda with Golang and Datadog
For the example I’m using the very popular logrus library and then I’m setting the log formatter to be JSON
-
Best Logging Library for Golang
For choosing the candidates for the poll, I didn't do any thorough research. I was looking for a library to use in my project at work, and I ended up at sirupsen/logrus which was already being used by one of the dependencies in that project.
-
Follow up to previous post: I contributed to an open source project outside working hours despite being asked not to. I was fired. No legal action.
I contribute to OSS as part of my job on the regular. The company is good about contributing upstream, signing CLAs, and all that. We still work against private forks for two main reasons: 1. Some changes that we need are not accepted by maintainers based on philosophical or architectural reasons that we can’t otherwise work around. You’re beholden to then unless you publicly fork the repo which has other legal/PR overhead for the company and OSS political implications. 2. Maintainers in the past have taken down repos, renamed repos, or changed the licensing on repos that have left us in a lurch. We always build against our own private forks because we need predictability and can’t be beholden to some other party for business continuity. We sync them down from the public upstream at our leisure.
-
Sourcehut will blacklist the Go module mirror
If they change the case on their username on the other hand, the Go ecosystem explodes: https://github.com/sirupsen/logrus/issues/570#issuecomment-3...
-
Lies we tell ourselves to keep using Golang
Like, for example, some projects importing logrus with a capital L and some with a lowercase L, and go modules having no way to reconcile the two: https://github.com/sirupsen/logrus/issues/553
-
go-coffeeshop - A practical coffee shop application event-driven microservices built with Golang
Ugh. Wish people would stop using logrus. It’s in maintenance mode and slow, especially its stack tracing.
- Criando uma API Rest com Fiber - Uma história pessoal de aprendizado
pgx
Posts with mentions or reviews of pgx.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-22.
-
Setting up a Database Driver, Repository and Implementation of a transaction function for your Go App
Sometimes, backend developers tend to opt for an ORM library because it provides an abstraction between your app and the database and thus there is little or no need to write raw queries and migrations which is nice. However, if you want to get better at writing queries (SQL for example), you need to learn how to build your repositories without an ORM. To open a database handle, you can either do it directly from the database driver or do it from database/sql with the driver passed into it. I will be opening the connection with database/sql together with pgx which is a driver and toolkit for PostgreSQL. Walk with me.
-
The DDD Hamburger for Go
The infrastructure layer contains the concrete implementation of the repository domain interface ActivityRepository in the struct DbActivityRepository. This repository implementation uses the Postgres driver pgx and plain SQL to store the activity in the database. It uses the database transaction from the context, since the transaction was initiated by the application service.
-
Building RESTful API with Hexagonal Architecture in Go
For building the RESTful Point of Sale service API, I've considered and selected a combination of technologies that would work seamlessly together. For handling HTTP requests and responses, using the Gin HTTP web framework would make sense because I think it seems complete and popular among Go community too. To ensure data integrity and persistence, I'm using PostgreSQL database with pgx as the database driver, the reason I choose PostgreSQL because it is the most popular relational database to use in production and offers efficient Go integration. I'm also implementing caching using Redis with go-redis client library, which provides powerful in-memory data storage capabilities.
-
Working with postgres in GO.
If you are willing to commit to working only with Postgres, I highly recommend pgx. Be sure you get the latest version github.com/jackc/pgx/v5. This gives you the full power of interacting with Postgres without going through an intermediate lowest-common-denominator library.
-
How to Use Iris and PostgreSQL for Web Development
It uses pg package and pgx driver under the hood.
-
Could I get a code review?
Starting off, is there any reason you're calling out to the CLI, instead of just using a Postgres driver like pgx? Shelling out to the command line should always be a last resort where possible as a software engineer.
-
Why elixir over Golang
For maintaining state I use PostgreSQL. Driver: https://github.com/jackc/pgx (I use the pgxpools) Along with Sqlc for generating database models and allowing me to focus on just building queries in DBeaver. https://sqlc.dev/
-
Make psql display settings on login
An example of what I'm looking for can be found here https://github.com/jackc/pgx/wiki/Getting-started-with-pgx-through-database-sql/c9f798b4d9a500fcf93931df2464af969d68f516
-
Zig now has built-in HTTP server and client in std
Except pgx recommends using their native interface, not database/sql, for performance and extra features [0], so it's not that simple in practice.
[0]: https://github.com/jackc/pgx#choosing-between-the-pgx-and-da...
-
Go Roadmap
pgx is “PostgreSQL driver and toolkit for Go”. Take a look at https://github.com/jackc/pgx
What are some alternatives?
When comparing logrus and pgx you can also consider the following projects:
zap - Blazing fast, structured, leveled logging in 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
glog - Leveled execution logs for Go
pq - Pure Go Postgres driver for database/sql
lumberjack - lumberjack is a log rolling package for Go
gomock - GoMock is a mocking framework for the Go programming language.
slog
go-sql-driver/mysql - Go MySQL Driver is a MySQL driver for Go's (golang) database/sql package
log15 - Structured, composable logging for Go
sqlc - Generate type-safe code from SQL