In this two-part series, we’ll dig deep into Solid Queue’s internals, discover what makes it unique, and learn more about why it was created in the first place.
Read in full here:
1 Like
Very good read that details the meaning of all the tables Solid Queue creates. I am curious to see how performant this is with so many processes running, but it would be nice to have job data right in the database. I have used DB driven job processing in the past and of course run into issues with jobs stuck in running state and other problems, looks like 37 signals has some solutions. It will be interesting to see how they work out in a production environment.
1 Like