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 data in there? Although an application can write events directly to Elasticsearch, this can become a bottleneck
😱 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, this will give peace of mind and a high degree of confidence in the disaster recovery plans.
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 was no exception, having started out years ago with the SQL-backed delayed_job, moving shortly thereafter to