go-lifecycle
Simple and flexible Go lifecycle manager library. (by g4s8)
run
A universal mechanism to manage goroutine lifecycles (by oklog)
| go-lifecycle | run | |
|---|---|---|
| 1 | 7 | |
| 1 | 1,472 | |
| - | 2.2% | |
| 5.7 | 4.5 | |
| about 1 month ago | about 1 month ago | |
| Go | Go | |
| MIT License | Apache License 2.0 |
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.
go-lifecycle
Posts with mentions or reviews of go-lifecycle.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-28.
run
Posts with mentions or reviews of run.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-26.
-
App init and graceful watch lib recommendations ?
What I’ve done in the past is use a run group (like https://github.com/oklog/run ) and one of the goroutines in the group is just listening for a SIGINT/SIGTERM/etc. When it sees that it throws an error which cancels the root context and let’s each component handle its own graceful shutdown
-
Simple and flexible Go lifecycle manager library.
Just a bit of feedback. https://github.com/oklog/run is great and simple way of handling goroutines. It doesn't bake in signal handing, health checking, retries, because those are technically all separate concerns, that can be independently implemented. When I read your Readme, the lifecycle part immediately made me think of oklog/run.
-
How do i gracefully handle both a program interrupt, and goroutines finishing?
I would suggest to use this library https://github.com/oklog/run It is really helpful to manage goroutines lifecycles.
-
The Go way of combining multiple components in one application
https://github.com/oklog/run Sounds like you’re looking for something like this.
- Gracefully shutting down multiple servers in a single prorgam
-
Goshutdown: terminate your goroutines gracefully and in a timely manner
How does it compare to https://github.com/oklog/run?
-
Don't Panic: Catching Panics in Errgroup
There is an interesting discussion which has an alternative view that, with few exceptions, panics should crash your program. I'm ok with that in development and testing, but would rather sleep soundly at night.
What are some alternatives?
When comparing go-lifecycle and run you can also consider the following projects:
fx - A dependency injection based application framework for Go.
kratos - Your ultimate Go microservices framework for the cloud-native era.
errgroup - Drop in replacement for errgroup that converts panics to errors
koanf - Simple, extremely lightweight, extensible, configuration management library for Go. Support for JSON, TOML, YAML, env, command line, file, S3 etc. Alternative to viper.
go-service
appctl - Application Controller