suture | viper | |
---|---|---|
14 | 74 | |
1,272 | 25,862 | |
- | - | |
5.7 | 8.8 | |
about 2 months ago | 4 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.
suture
-
Could I get a code review?
This one is highly specialized, but I'm a huge fan of Suture for managing long lived goroutines.
-
[gopulse/pulse] the Golang framework designed to ensure your web services stay alive.
In English, your phrasing doesn't come off as a play on words/a reference to the name, so much as it describes a feature of the library. The expectation is, with the description you've given it, the library would handle some form of resilience in service management. I half expected the library to be similar to Suture.
-
Ergo: Erlang/OTP Implemented in Golang
It does not give you a way to reliably track arbitrary goroutines that "this" goroutine (for whatever that may be) wants to track, the way an Erlang process can just "link" to anything it is capable of naming the PID for.
However, you can construct a reliable mechanism where one goroutine can start another and know whether or not the one it started has failed by using the available primitives, as I did in https://github.com/thejerf/suture . It's an easier problem since there's no cluster and no network that can get in the way. I've also done the exercise for the network case: https://pkg.go.dev/github.com/thejerf/reign#Address.OnCloseN... but that only functions within the network defined by that library because, again, it just isn't arbitrarily possible.
(I suppose it's relevant to some of my other comments to point out that I've also implemented basically Erlang-style concurrency in Go, with network, but as a relatively idiomatic translation rather than a blind one.)
-
Is there an equivalent to Elixir / GenServer in Go? Trying to create the same request / response pattern with better performance but not sure where to start.
If you also want Supervisor-like behavior, take a look at suture.
-
Start an already running service: no error, error, or panic?
For context, I've been working with similar interfaces for many years through suture.
-
Erlang vs Golang
I wrote suture for idiomatically-ported supervisor trees (that is, the ways they differ are deliberately chosen, not accidents), and reign for Go-native cluster-like support. I use suture in almost everything I write. Reign is used on production services but I don't generally use it because I think modern stacks have better options with modern message busses, but it can be useful for porting.
- Erlang-ish supervisor trees for Go
-
How “let it fail” leads to simpler code
I think the distinction between expected and unexpected errors can easily fall through the cracks and writing code in a way that an unexpected error doesn’t break everything is quite powerful.
Golang makes it easy to ignore errors that can be ignored and defer/recover provide a way to implement a way to “let it fail”
There’s even an implementation of supervisor trees for Go [0] :)
[0] https://github.com/thejerf/suture
-
Golang vs Elixir protoactor supervision
(If you'd like something lighter weight, suture is a supervisor library without a whole lot of other stuff. If you want that other stuff, by all means, go to town.)
-
The method to manage multiple services in a process.
This is the primary reason almost every program I write ends up using suture. The restarting is nice when it works, but Go code is often reasonably robust. (Not 100%, but reasonably.) But it's a nice organization principle.
viper
-
Upload and Delete file from Amazon S3 Bucket in Go using Presigned URLs
Once environment variables are setup we need load them into our project. For this this i will use viper
-
Proxy Server in Go
The code uses Viper to load configuration files in the application.
- API completa em Golang - Parte 2
-
What 3rd-party libraries do you use often/all the time?
github.com/spf13/viper
- API completa em Golang - Parte 1
-
Building RESTful API with Hexagonal Architecture in Go
Instead of directly accessing environment variables with os.Getenv(), integrating a configuration handler like viper might make it maintainable.
-
What is the most common approach to configure a backend app?
I guess most people are using https://github.com/spf13/viper but I don't know if I should read everything from
-
Could I get a code review?
Use Viper for config file or environmental variable configuration -- it's going to save you a whole lot of time.
-
Which packages do you recommend for building cli tools?
Cobra and Viper.
-
Library for Python similar to Go's Viper / 12 Factor
I've mostly been using https://github.com/spf13/viper of late for my go projects. It supports the standard config formats, (json, yaml, toml etc) and lets you override any value with a ENV value.
What are some alternatives?
rustig - A tool to detect code paths leading to Rust's panic handler
godotenv - A Go port of Ruby's dotenv library (Loads environment variables from .env files)
protoactor-go - Proto Actor - Ultra fast distributed actors for Go, C# and Java/Kotlin
envconfig - Small library to read your configuration from environment variables
bastion - Highly-available Distributed Fault-tolerant Runtime
koanf - Simple, extremely lightweight, extensible, configuration management library for Go. Support for JSON, TOML, YAML, env, command line, file, S3 etc. Alternative to viper.
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
cleanenv - ✨Clean and minimalistic environment configuration reader for Golang
reign - Rewrite Erlang In Go Nicely - a library for mimicking Erlang's mailboxes and clustering
kelseyhightower/envconfig - Golang library for managing configuration data from environment variables
ergo - An actor-based Framework with network transparency for creating event-driven architecture in Golang. Inspired by Erlang. Zero dependencies.
mapstructure - Go library for decoding generic map values into native Go structures and vice versa.