You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 20, 2023. It is now read-only.
Hi everyone 👋 que-go was a fun but brief experiment for me ~9 years ago. I was never happy enough with the architecture and design to continue supporting it.
However, I recommend you check out my new project, River. River already does quite a bit more than que-go, uses a much more scalable design, and is designed for modern Go and pgx/v5. Brandur and I are hoping to make River into the Postgres job queue we always wanted to see in the Go ecosystem.
Thank you! ✌️
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi everyone 👋 que-go was a fun but brief experiment for me ~9 years ago. I was never happy enough with the architecture and design to continue supporting it.
However, I recommend you check out my new project, River. River already does quite a bit more than que-go, uses a much more scalable design, and is designed for modern Go and pgx/v5. Brandur and I are hoping to make River into the Postgres job queue we always wanted to see in the Go ecosystem.
Thank you! ✌️
The text was updated successfully, but these errors were encountered: