go-coffeeshop
zap
go-coffeeshop | zap | |
---|---|---|
10 | 51 | |
3,952 | 20,981 | |
- | 1.0% | |
0.0 | 8.1 | |
12 months ago | 6 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.
go-coffeeshop
- Could you share an microservices architecture having synchronous and async(kafka) and Caching(Redis) used in your Organization.
-
Portfolio ideas for backend
For the current competition, something like this will make you stand out
- Good repos to learn microservices in go
- Go project written in clean code architecture
- A coffee shop application with event-driven microservices in Golang
- A practical event-driven microservices demo built with Golang. Nomad, Consul Connect, Vault, and Terraform for deployment
-
go-coffeeshop - A practical coffee shop application event-driven microservices built with Golang
And where is the domain model? https://github.com/thangchung/go-coffeeshop/blob/main/internal/product/domain/models.go
-
Where to learn gRPC to build projects
You can find the standard structure which used golang with gRPC-gateway at https://github.com/thangchung/go-coffeeshop. Hope it helps
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?
paper-plane-backend - To make an account web-application for my alone life.
logrus - Structured, pluggable logging for Go.
grpc-starter-kit
zerolog - Zero Allocation JSON Logger
buf - The best way of working with Protocol Buffers.
slog
golangcleanStartingpoint - Golang clean architecture starting point
glog - Leveled execution logs for Go
wild-workouts-go-ddd-example - Go DDD example application. Complete project to show how to apply DDD, Clean Architecture, and CQRS by practical refactoring.
go-log - a golang log lib supports level and multi handlers
go-clean-arch - Go (Golang) Clean Architecture based on Reading Uncle Bob's Clean Architecture
log - Structured logging package for Go.