logo
zap
logo | zap | |
---|---|---|
24 | 52 | |
5 | 21,040 | |
- | 1.3% | |
0.0 | 8.1 | |
almost 3 years ago | 7 days ago | |
Go | ||
Creative Commons Attribution 4.0 | 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.
logo
-
Ask HN: Good examples of Go back ends?
Most golang backends I've seen meanwhile use or switched to using the "gin" framework to build their APIs.
A lot of them also have conventions for the frontend, where the assets usually are stored in /public, so they can be go:embed later as an embed.FS instance into the binary.
Having said that, there's plenty of examples on github. I'd recommend to take a look at bigger projects or templates and understand how they structured their packages and abstraction levels. E.g. go-admin comes to mind [1]
[1] https://github.com/GoAdminGroup/go-admin
[2] https://github.com/gin-gonic/gin
-
From Laravel to Sponge: How to Easily Develop Web Services with Golang
Excellent Performance: Sponge is built on the gin framework, providing outstanding performance for web service development.
- 6 🔥 Awesome Golang packages (web devs)
-
Generate project code for a general web service(gin) to increase your development efficiency by 10 times
The web framework uses gin. It also includes swagger documents, common service governance function codes, and build and deployment scripts. You can choose which database to use.
-
Gin - HTTP web framework written in GO.
GIN
- How to run background functions in go
-
Fundamentals to Learn
When it comes to Web Development I would recommend taking a closer look at some standard library packages like net and encoding. Looking at some Web Development open-source frameworks / libraries might be helpful as well. Gin is one of them.
-
Tools besides Go for a newbie
IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
-
Looking to build a small team for a start-up idea
The back-end is going to be written in Golang, using a Gin, Gorm, and a Postgres DB, so bonus points if you are familiar with Go!
-
Can an API be merely a server that has post requests sent to it, rather than something that is installed?
Here's Express for Node.js, Flask for Python, Alfred for Dart, and Gin for Go; that's four different software packages for four completely different programming languages that all do very similar things. Take a look and see which one feels best, and start from there!
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?
recipe-gin-postgres-api - Example of a go HTTP api using gin in zerops.io
logrus - Structured, pluggable logging for Go.
viper - Go configuration with fangs
zerolog - Zero Allocation JSON Logger
todo-api-microservice-example - Go microservice tutorial project using Domain Driven Design and Onion Architecture!
slog
yaml - YAML support for the Go language.
glog - Leveled execution logs for Go
Express - Fast, unopinionated, minimalist web framework for node.
go-log - a golang log lib supports level and multi handlers
Squirrel - Fluent SQL generation for golang
log - Structured logging package for Go.