Dave Copeland Dec 19, 2023

re: Solid Queue

That Redis is fast is certainly a benefit to using e.g. Sidekiq, but it's not really the main reason you want your jobs in Redis. The reason is that you don't want your jobs in the same database as your operational data.

I don't think 37signals are making anything up, but just remember that their tech leadership has extremely limited experience and that dismissing the collective wisdom built on decades of experience is not something to do lightly.

Show threadDamaxDec 20, 2023
@davetron5000 Rails itself allows multiple databases to be configured and use on a per-model basis. Does Solid Queue restricted to use the same database as the rest of the data?
Show threadDave Copeland Dec 20, 2023
@Damax It looks like you can set your queue DB to be different, but then what is the point? Why not keep life simple and use Sidekiq?
Show threadTodd A. Jacobs | Rubyist
@davetron5000 @Damax Unlike #resque, #sidekick reserves certain features for commercial licenses. I can see why an open source framework might want to find a truly #FOSS alternative that will be maintained alongside the framework itself.
Dec 30, 2023 at 6:39pmWeb
Show threadDave Copeland Dec 30, 2023
@todd_a_jacobs @Damax I would be surprised if resque has any of sidekiq’s paid features
Show threadTodd A. Jacobs | RubyistDec 30, 2023
@davetron5000 @Damax Probably not, but that's kind of an argument for Rails building something new that doesn't require upstream support or commercial licenses. Last I checked, #resque was struggling to find #maintainers, so a fresh start may be warranted. You'd have to look at their open issues and code to form your own opinion, though.
Show threadDave Copeland Dec 30, 2023
@todd_a_jacobs @Damax they could’ve easily invested in resque and not started from scratch. They could’ve adapted GoodJob to MySQL if they were dead set on using a DB. But those are less fun options I guess.
Show threadTodd A. Jacobs | RubyistDec 30, 2023

@davetron5000 @Damax Not #MySQL; it's no longer fully #FOSS, but #MariaDB is. You'd have to look at #resque yourself before deciding to fork it, fix it, find alternatives, or build something new. I don't have the strong opinion you do about that, but will assume that someone gave it more than a passing thought.

New isn't always better, but neither is it inherently #NIHsyndrome. Nothing prevents using other #DBs, #ORMs, or #queues if willing to forego #conventionoverconfiguration.