Andrew Snow

At Chargify, we lean heavily on Elasticsearch for data storage as well as search, but upgrading Elasticsearch major versions requires a full cluster restart. We came up with a plan for upgrading with

In order to upgrade Elasticsearch in-place from v2 to v5, one of the road blocks we faced was that the built-in upgrade feature did not support indexes created with v1 of Elasticsearch. We

Applications that generate a stream of events need a way to store them centrally for search and analysis. Elasticsearch is a decent choice for aggregating event logs, but how do you get the

😱 A nightmare scenario for any business: needing a backup that isn't there! Procedures for performing and verifying backups have always been necessary, and if this can happen regularly, automatically, monitored for any failures,

In this final part, the locking techniques in Chargify's background job system will be explained. Commonly you need a job to run only one at a time, no matter how many there are

Here's a few more interesting aspects of our background job system. Make sure to check out part 1 first if you haven't already. Callbacks We've created several callbacks for job classes to use:

Many Rails apps have some kind of job queue. While the "out of the box" experience with Rails and Sidekiq keeps getting better over time, here's a collection of ways we've

Redis is an in-memory database which has become the default choice for background job queues in Rails applications, because it helps with scaling to large numbers of background job workers. The Chargify application