Repository navigation
DOC-7315 Add Resque, Asynq, and Hangfire integration pages - #4603
Merged
andy-stark-redis merged 1 commit intoNov 17, 2026
Merged
andy-stark-redis merged 1 commit into
andy-stark-redis merged 1 commit into
Conversation
Adds content/integrate/resque, asynq, and hangfire, and links them from the job-queue use case's Ecosystem section. Also removes the Spring Batch bullet: it claimed a "Redis job repository", but spring-batch-core 6.0.6 and 6.1.0-RC1 contain only a MongoDB one. The Hangfire bullet now says its Redis storage is a community package. Bull is left alone; it is in maintenance mode and points to BullMQ. Every snippet was run against Redis 7.2.7 with Resque 3.2.0 (Ruby 4.0.6), Asynq 0.26.0 (Go 1.27.2), and Hangfire.Core 1.8.25 with Hangfire.Redis.StackExchange 1.12.0 (.NET 9). The three behave differently when a worker is killed with kill -9. Resque never re-runs the job: with the default 60 second heartbeat and 300 second prune interval a later worker marks it failed as Resque::DirtyExit, and with 2 and 6 seconds that happened 5 seconds after the kill. Asynq holds a lease on each active task, so the task stayed active for about a minute, moved through retry and pending, and a new server re-ran it about 73 seconds after the kill. Hangfire leaves the job in a dequeued list until the storage InvisibilityTimeout (30 minutes by default) passes; with 10 seconds, a new server re-ran it 62 seconds after the kill. Asynq and Hangfire both poll for scheduled and retried jobs, about every 5 and 15 seconds, so short delays are not accurate. Hangfire core has no Redis storage. The vendor's Redis package, Hangfire.Pro.Redis, is part of the paid Hangfire Pro, and the page documents the community package Hangfire.Redis.StackExchange (LGPL v3, listed on Hangfire's extensions page, no official support) and says which is which. Pricing is deliberately not stated. Learned: Resque, Asynq, and Hangfire recover a killed worker's job in three different ways (never, lease expiry, invisibility timeout); Hangfire's Redis storage is a community package Constraint: Kill-recovery and polling numbers come from single-server runs on the versions named; recheck if a library changes how it recovers or polls Directive: Do not say Hangfire supports Redis without naming the community package, and do not state Hangfire Pro pricing Gaps: Resque plugins for retry and scheduling not run; Asynq unique tasks, periodic tasks, and Redis Cluster not run; Hangfire dashboard, recurring jobs, and Hangfire.Pro.Redis not run; links to upstream docs are site roots, not deep pages Recheck: when Resque 4, Asynq 1.0, or Hangfire 2.0 ships Ticket: DOC-7315 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Contributor
Contributor
Contributor
🧠 Redis MemoryFound 5 related items from repository history (5 new this commit):
Memory updated at f23866a |
andy-stark-redis
deleted the
DOC-7315-add-resque-asynq-and-hangfire-integration-docs
branch
November 17, 2026 16:15
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
content/integrate/: Resque (Ruby), Asynq (Go), and Hangfire (.NET), following the Celery page's shape.Verification
Every snippet was run against Redis 7.2.7 with Resque 3.2.0, Asynq 0.26.0 (Go 1.27), and Hangfire.Core 1.8.25 with Hangfire.Redis.StackExchange 1.12.0 (.NET 9). The kill-recovery behavior differs for each:
Resque::DirtyExit) once the dead worker's heartbeat is older than the prune interval (300 s by default).activefor about a minute, then retries; a new server re-ran it about 73 s after the kill.dequeuedlist until the storageInvisibilityTimeoutpasses (30 min by default). With 10 s, a new server re-ran it 62 s after the kill.For review
Hangfire.Pro.Redis) is part of the paid Hangfire Pro, so the page documents the communityHangfire.Redis.StackExchange(LGPL v3, third-party, no official support) and says which is which. Pricing is not stated.spring-batch-core6.0.6 and 6.1.0-RC1 contain only a MongoDB job repository, so I removed the bullet, as agreed.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only changes with no runtime or application code impact.
Overview
Adds three new integration guides—Resque (Ruby), Asynq (Go), and Hangfire (.NET)—aligned with existing pages like Celery: setup, enqueue/work patterns, Redis key layout, and behavior when a worker or server is killed.
The job-queue Ecosystem section now links to these docs instead of external URLs, drops the Spring Batch Redis job-repository entry, and clarifies that Hangfire’s Redis backing is via a community storage package (not core Hangfire).
Reviewed by Cursor Bugbot for commit f23866a. Bugbot is set up for automated code reviews on this repo. Configure here.