Ditch Redis: Embrace SolidQueue in Rails 8

Ditch Redis: Embrace SolidQueue in Rails 8

Category: Technology
Duration: 3 minutes
Added: January 15, 2026
Source: www.simplethread.com

Description

In this episode of Tech Talk, we explore a transformative shift in the Ruby on Rails community as Rails 8 eliminates Redis from its default stack. Join host and expert Matt Kelly as we delve into the advantages of SolidQueue, SolidCache, and SolidCable—new tools that leverage PostgreSQL for job processing, caching, and real-time updates. Discover the hidden costs of using Redis, including server management and network overhead, and learn how SolidQueue simplifies your architecture by using a single data store. We'll also discuss the migration process from Sidekiq to SolidQueue and how to effectively transition your job queues. Tune in for insights that can enhance your development workflow and lead to more efficient systems.

Show Notes

## Key Takeaways

1. Rails 8 moves away from Redis, introducing SolidQueue, SolidCache, and SolidCable for simplified architecture.
2. The costs of using Redis include server management and network overhead.
3. SolidQueue retrieves jobs efficiently from PostgreSQL using the SKIP LOCKED feature.
4. Transitioning from Sidekiq to SolidQueue requires understanding the new tools and migrating job queues.

## Topics Discussed

- The rise of Redis in Rails applications
- Overview of SolidQueue and its benefits
- Cost considerations for Redis
- How SolidQueue simplifies job processing
- Steps for migrating from Sidekiq to SolidQueue

Topics

Rails 8 SolidQueue Redis alternatives PostgreSQL job processing caching real-time updates software development Sidekiq migration Rails architecture database management SolidCache SolidCable tech podcast

Transcript

H

Host

Welcome back to Tech Talk, everyone! Today, we’re diving into a significant change in the Ruby on Rails community. With the release of Rails 8, Redis is no longer part of the default stack. To help us understand this shift and what it means for developers, we have Matt Kelly, an expert in software development. Welcome, Matt!

E

Expert

Thanks for having me! Excited to be here.

H

Host

So, Matt, let's start with the basics. Why was Redis such a popular choice for Rails applications in the first place?

E

Expert

Great question! Redis is known for its speed and reliability. It's a key-value store that excels in job queuing, caching, and real-time messaging, which made it the go-to choice for many developers over the years.

H

Host

That makes sense! But now, Rails 8 has introduced something called SolidQueue, SolidCache, and SolidCable as alternatives. Can you explain how these work?

E

Expert

Absolutely! Essentially, these new tools leverage your existing relational database, like PostgreSQL, to manage job queues, caching, and real-time messages. Instead of relying on a separate system like Redis, you can simplify your stack by using what you already have.

H

Host

Sounds promising! But I'm sure there are some complexities involved. What are some of the costs associated with using Redis that developers need to consider?

E

Expert

Well, beyond the hosting costs, you have to think about server management—deploying, versioning, and monitoring the Redis server. Plus, you need to configure persistence strategies and manage memory limits. There’s also the overhead of ensuring network connectivity and maintaining high availability.

H

Host

Yikes! That does sound complicated. How does SolidQueue simplify things?

E

Expert

In a 'Redis-less' Rails setup, if either Rails or PostgreSQL fails, everything stops. This makes debugging much simpler because you're working with a single data store rather than juggling two different systems.

H

Host

That’s a significant improvement! Now, could you break down how SolidQueue actually retrieves jobs from the database?

E

Expert

Sure! It uses a SQL command with a nice feature called SKIP LOCKED. When a worker needs a job, it runs a query that selects the next available job while avoiding locked rows. This means that workers don’t wait on each other, which dramatically improves performance.

H

Host

That’s a clever way to handle things! So, if a developer wants to transition from Sidekiq to SolidQueue, what’s the first step?

E

Expert

The first step is to familiarize yourself with the new tools and their configurations. Then, you can begin to migrate your job queues over to SolidQueue using your existing PostgreSQL setup.

H

Host

Thanks for that insight, Matt! It sounds like Rails 8 is paving the way for a more streamlined development process. Any final thoughts?

E

Expert

Just that embracing simplicity in technology can lead to more efficient systems. It's all about finding the right tools that fit your needs without adding unnecessary complexity.

H

Host

I love that takeaway! Thanks for joining us today, Matt. We appreciate your expertise.

E

Expert

Thank you! Glad to be here.

H

Host

And thank you to our listeners for tuning in! We’ll catch you next time on Tech Talk.

Create Your Own Podcast Library

Sign up to save articles and build your personalized podcast feed.