starred/asynq

Fork 0

mirror of https://github.com/hibiken/asynq.git synced 2026-04-26 07:25:56 +03:00

[GH-ISSUE #385] [QUESTION] Production ready ? #168

New issue

Closed

opened 2026-03-02 05:19:17 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 05:19:17 +03:00

Owner

Originally created by @thejosk on GitHub (Jan 24, 2022).
Original GitHub issue: https://github.com/hibiken/asynq/issues/385

Originally assigned to: @hibiken on GitHub.

Hi @hibiken,

First of all, thanks for this amazing library, excellent job.

We plan to use this library for background job processing for a new project in our company (>10 years in the industry). I know you've mentioned in https://github.com/hibiken/asynq#stability-and-compatibility that there could be breaking changes until a major version is released, I'm wondering if anything has changed and how breaking could this changes be?, What would you suggest ?

Thanks again.

Originally created by @thejosk on GitHub (Jan 24, 2022). Original GitHub issue: https://github.com/hibiken/asynq/issues/385 Originally assigned to: @hibiken on GitHub. Hi @hibiken, First of all, thanks for this amazing library, excellent job. We plan to use this library for background job processing for a new project in our company (>10 years in the industry). I know you've mentioned in https://github.com/hibiken/asynq#stability-and-compatibility that there could be breaking changes until a major version is released, I'm wondering if anything has changed and how breaking could this changes be?, What would you suggest ? Thanks again.

kerem

2026-03-02 05:19:17 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-02 05:19:18 +03:00

Author

Owner

@hibiken commented on GitHub (Jan 24, 2022):

Hi @thejosk, thank you for posting this question!

I believe that README needs an update, since the library is quite stable at this point.
Breaking changes are rare at this point, and if we need to make such changes, we document thoroughly in the release notes and CHANGLOG. So as long as you use go.mod to specify the version number for asynq, it's unlikely to break your application.

Also, if we make changes in the schema we use to store tasks and metadata in redis, we provide the migrate command via the CLI to upgrade to a new version (but I don't foresee any such change coming in the future at this point).

Please let me know if you have more concerns or follow up questions 👍

@hibiken commented on GitHub (Jan 24, 2022): Hi @thejosk, thank you for posting this question! I believe that README needs an update, since the library is quite stable at this point. Breaking changes are rare at this point, and if we need to make such changes, we document thoroughly in the release notes and CHANGLOG. So as long as you use go.mod to specify the version number for asynq, it's unlikely to break your application. Also, if we make changes in the schema we use to store tasks and metadata in redis, we provide the `migrate` command via the CLI to upgrade to a new version (but I don't foresee any such change coming in the future at this point). Please let me know if you have more concerns or follow up questions 👍

kerem commented

2026-03-02 05:19:18 +03:00

Author

Owner

@thejosk commented on GitHub (Jan 24, 2022):

Awesome, thank you. Closing this for now.

@thejosk commented on GitHub (Jan 24, 2022): Awesome, thank you. Closing this for now.

kerem referenced this issue

2026-03-07 22:05:07 +03:00

[GH-ISSUE #168] [FEATURE REQUEST] CLI/server for running exec.Command #1068

kerem referenced this issue

2026-03-15 19:03:28 +03:00

[GH-ISSUE #168] [FEATURE REQUEST] CLI/server for running exec.Command #2077

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/asynq#168

No description provided.

Rows
Columns