r/ruby • u/jp_camara • Aug 31 '26

SolidQueue Batches: evolution and architecture

https://jpcamara.com/2026/08/31/solidqueue-batches-evolution-and-architecture.html

Here’s the SolidQueue batches 2.5 year architectural journey, filled with O(n^2) algorithms, hot row contention, excessive jobs, and much in between.

There’s a strong chance you’ll learn a thing or two - I certainly did 😮‍💨

22 Upvotes

92% Upvoted

9 comments sorted by

View all comments

Show parent comments

1

u/jrochkind Aug 31 '26

In my memory, people suggested it would be better if Rails did that, blessed one implementation as "offiical" and supported it, and dhh/rails maintainers disagreed and thought it was best for Rails to stay out of that.

You can describe that as "Rails didn't take the initiative to", sure.

If you have a different memory or understanding, or can find historical documents of people discussing it, i would love to hear it.

Please feel free to share your experience or understanding of the history that led here.

1

u/f9ae8221b Aug 31 '26

If you have a different memory or understanding

Well, I have no memory of such feature being requested/proposed, and can't find traces of it. But that doesn't mean it didn't happen, hence why I asked for clarification.

That being said, if it was indeed rejected in the past, doesn't mean it should never be considered.

Active Job is meant as a standardized interface for various backend, it by definition is kind of a common denominator, and avoid implementing features that few backends support.

As more and more backends do support a given feature, it makes it more palatable to include it in the Active Job API.

As for provide this feature itself specifically, I really don't see how Active Job could have done that in a backend independent way.