rmax/scrapy-redis

Redis-based components for Scrapy.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 57 minutes ago
Added to GitGenius on September 12th, 2026
Created on August 29th, 2011
Open Issues & Pull Requests: 43 (+0)
GitHub issues: Enabled
Number of forks: 1,585
Total Stargazers: 5,643 (+0)
Total Subscribers: 265 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.8 hours
Mean response time: 59.3 days
90th percentile: 259.9 days
Tracked items: 7

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 3
Closed in 7 days: 0
Avg open age: 353 days
Stale 30+ days: 5
Stale 90+ days: 5

Recent activity

Opened in 7 days: 3
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Scrapy-Redis is a set of Redis-based components for Scrapy that enable distributed crawling and scraping across multiple worker instances.

The tool solves the problem of scaling web scraping operations by using Redis as a shared message broker. Instead of each spider maintaining its own queue, multiple Scrapy instances connect to a central Redis server to coordinate work. The project provides plug-and-play replacements for Scrapy's scheduler, duplication filter, and item pipeline, allowing developers to add distributed capabilities with minimal code changes. It also supports distributed post-processing, where scraped items are queued in Redis for consumption by separate processing workers. The tool includes support for JSON-formatted data in Redis, allowing requests to carry nested metadata that spiders can access through standard Scrapy request attributes.

Scrapy-Redis suits teams running broad, multi-domain crawls that benefit from horizontal scaling. It is best for scenarios where you can tolerate basic work distribution without advanced features like URL expiration or sophisticated prioritization strategies. The README notes that Frontera is an alternative for projects requiring more complex crawl frontier capabilities and advanced URL prioritization.

The project maintains automated testing across multiple Python versions and runs security checks as part of its continuous integration pipeline. Code coverage is tracked and reported. The tool is actively maintained with documentation hosted externally and a structured contribution process documented in the repository wiki.