upspin
zap
Our great sponsors
upspin | zap | |
---|---|---|
20 | 51 | |
6,219 | 20,894 | |
0.2% | 1.4% | |
6.0 | 8.1 | |
17 days ago | 6 days ago | |
Go | Go | |
Apache License 2.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.
upspin
-
I Moved My Blog from IPFS to a Server
Super intriguing. Thanks for sharing!
It reminds me a bit of an early Go project called Upspin [1]. And also a bit of Solid [2]. Did you get any inspiration from them?
What excites me about your project is that you're addressing the elephant in the room when it comes to data sovereignty (~nobody wants to self-host a personal database but their personal devices aren't publicly accessible) in an elegant way.
By storing the data on my personal device and (presumably?) paying for a managed relay (and maybe an encrypted backup), I can keep my data in my physical possession, but I won't have to host anything on my own. Is that the idea?
-
Educational Codebases
There are a few Go projects meant to be learned from:
- https://github.com/pion/opus for to learn audio
- https://github.com/benbjohnson/wtf for overall production quality
- https://github.com/upspin/upspin difficult to explain, personally I'm not a fan of the errors
-
Fundamentals to Learn
You could also take a look at some real-world open-source projects. I like upspin for its idiomatic approach.
- Examples of Good Go Repos
- Examples of an idiomatic API project
-
Best practices of validation on web apps?
For example, Rob Pike's upspin places all its validations in the separate package. Do you agree with that approach? Which yet proven options there are?
- Is there a good example of an open source non-trivial (DB connection, authentication, authorization, data validation, tests, etc...) Go API?
-
Ask HN: What Are You Working on This Year?
Just a few projects that could perhaps interest you in terms of design of your own solution :
Upspin: https://upspin.io/
- Upspin: A framework for naming everyone's everything.
-
proposal: Go 2: error handling: try statement with handler
The early error wrapping work which emerged out of the Upspin project, that eventually made its way into the errors package, included stack traces in the wrap error. This would provide exactly what it appears you seek.
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.
-
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).
- 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?
mitchellh/cli - A Go library for implementing command-line interfaces.
logrus - Structured, pluggable logging for Go.
ytcast - cast YouTube videos to your smart TV from command-line
zerolog - Zero Allocation JSON Logger
golang-gin-realworld-example-app - Exemplary real world application built with Golang + Gin
slog
fiber-boilerplate - This is the go boilerplate on the top of fiber web framework. With simple setup you can use many features out of the box
glog - Leveled execution logs for Go
Rundeck - Enable Self-Service Operations: Give specific users access to your existing tools, services, and scripts
go-log - a golang log lib supports level and multi handlers
ivy - The Unified AI Framework
log - Structured logging package for Go.