provisioning-backend
taskq
provisioning-backend | taskq | |
---|---|---|
12 | 7 | |
13 | 1,202 | |
- | - | |
9.2 | 0.0 | |
4 days ago | 7 months ago | |
Go | Go | |
GNU General Public License v3.0 only | BSD 2-clause "Simplified" 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.
provisioning-backend
-
[Question] How do you guys separate your tooling for different version
I wrote a makefile which installs tools into PROJDIR/bin which is also in the gitignore.
-
Instrument a third party package
Extremely simple in go, you just implement what is called Doer interface (one method). Here is an example from one of my projects, it is a simple decorator with logger in this case. Then you just initialize the client with this instance, in my project it is slightly more complex because I also setup OpenTelemetry but you get the idea.
-
Can you really build a complete restful service without any frameworks?
Authentication and authorization is typically just a middleware which is essentially a function. Recently I implemented a RBAC functionality into our microservice which does not use any big framework. On our platform we have a RBAC service we need to call via REST. As you can see the whole patch is small if you exclude the generated OpenAPI client.
- In-memory key value store
-
Repository with sqlc, how to hide transactions?
We use DAO/DAL in our app and I ran into the same problem - DAO does not work well with transactions. We have our own WithTransaction function which is currently only used within one model and that works fine. But the problem appears when we want to do a transaction across several models - that needs to be done in the business (service) layer.
-
Is your makefile supposed to be a justfile?
Our project does have extensive makefile broken down into individual files so it is more readable. As you can see, we have targets for database, code quality, modules, testing, client generation, OpenAPI etc. It also has a trivial help:
-
Any references for open source mini workflow libraries or systems written in Go?
Here is our code: https://github.com/RHEnVision/provisioning-backend/tree/main/pkg/worker
- Want to know if this is a valid approach
- Cache headers when serving embedded files
-
When to use a queue library or straight redis?
Our solution is simply one Redis queue, jobs have "type" (string) and are marshalled via Gob (for type safety) and there is no return value from job or error. This makes things extremely easy. We keep statistics (metrics) of job queue size and "in flight" jobs. Here is our implementation, just for inspiration. I suggest to write this on your own: https://github.com/RHEnVision/provisioning-backend/tree/main/pkg/worker
taskq
-
What is the best task queue?
Hi, I'm starting a new project that involves distributing task on different (and possibly distributed) workers in Golang. So I'm looking for the best task queue library to use; for now the ones I like are the following (in no particular order): - asynq - machinery - taskq
-
Are there any actively maintained or official Golang libraries for managing work queues?
+ taskq
-
Golang task queue
I had a look at: 1. machinery - https://github.com/RichardKnop/machinery 2. go-celery - https://github.com/gocelery/gocelery 3. asynq - https://github.com/hibiken/asynq 3. taskq - https://github.com/vmihailenco/taskq
-
How to plan and execute a large number of tasks in Go?
Oh my god, I have to deal with a similar system at work and I wish we hadn't tried to handroll this. If its possible you should look into something off-the-shelf. Could Celery work for 1000*10000 tasks? But if you must do it yourself, https://github.com/vmihailenco/taskq looks good
- Redis messaging queue suggestions
-
Kafka Message Task Queue
I was looking at https://github.com/vmihailenco/taskq to use potentially to manage tasks being picked up by a set of workers. Since we already have a Kakfa expertise I was looking to potentially use that instead.
- Switching from Celery and Python to Go
What are some alternatives?
goyek - Task automation Go library
machinery - Machinery is an asynchronous task queue/job queue based on distributed message passing.
spok - It's a build system Jim, but not as we know it 🖖
Benthos - Fancy stream processing made operationally mundane
weaver - Programming framework for writing and deploying cloud applications.
Asynq - Simple, reliable, and efficient distributed task queue in Go
earthly - Super simple build framework with fast, repeatable builds and an instantly familiar syntax – like Dockerfile and Makefile had a baby.
gocelery - Celery Distributed Task Queue in Go
dejq - Very Simple Job Queue
go-jdeque - Chunk based deque for Go
lmstfy - A task queue with REST API
rmq - Message queue system written in Go and backed by Redis