I Love You, Redis, But I’m Leaving You for SolidQueue
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Rails 8 introduces SolidQueue, SolidCache, and SolidCable as PostgreSQL-based replacements for Redis in the default stack. SolidQueue leverages PostgreSQL's FOR UPDATE SKIP LOCKED feature to handle job queuing without lock contention, eliminating the operational complexity of maintaining Redis infrastructure. The article provides a complete migration guide from Sidekiq to SolidQueue, including setup instructions, recurring job configuration, and Mission Control monitoring. While Redis remains necessary for high-throughput applications processing thousands of jobs per second, SolidQueue handles 200-300 jobs/second and is sufficient for most Rails applications, as demonstrated by 37signals processing 20 million jobs daily on PostgreSQL.
Table of contents
The True Cost of RedisHow SolidQueue WorksScheduling Recurring Jobs with SolidQueueJob Concurrency: The Feature You Didn’t Know You NeededMonitor SolidQueue with Mission ControlThe Migration Path: From Sidekiq to SolidQueueWhen NOT To Use SolidQueuePractical Implementation GuideHow to Test SolidQueueCommon GotchasDoes it ScaleThe Bottom LineSort: