> Maybe worth it for some low-volume jobs. > ... > The lesson learned was queues at scale are hard distributed systems problems I'd go so far to say that w

> Maybe worth it for some low-volume jobs. > ... > The lesson learned was queues at scale are hard distributed systems problems I'd go so far to say that when you need such scale, Rails or Job Queues like Rails' are not the solution. Event-based architectures (event-sourced, event-buses, actors etc) are far better suited. Rather than trying to solve all the problems that those architectures were explicitly designed for in redis/sidekiq/rails, just move to those architectures. You won't have the nice "rails generate CreditCard" anymore /s, but you'll gain a lot of consistency, simplicity, performance and architectural sanity.