-
active-job-style-guide
This Background Jobs style guide is a list of best practices working with Ruby background jobs.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I know this doesn’t answer your question directly but I just wanted to point out that if you’re using Sidekiq, it’s at a minimum double as fast to run it directly without AJ, and potentially up to 20x faster. https://github.com/mperham/sidekiq/wiki/Active-Job#performance
To my best memory, when retries are exhausted, and I hope you mean Sidekiq retries, not Active Job's retries, Sidekiq raises an exception that Active Job catches and runs your error handler (that typically submits to Sentry/Rollbar). The job is moved to the Dead queue. I can't tell the details off the top of my head, the guide has an explanation why using Active Job retries with Sidekiq is a bad idea. https://github.com/toptal/active-job-style-guide#retries