Slack built a distributed cron execution system for scale by developing a new execution service written in Go and deployed on Bedrock. They faced issues with maintainability, cost-ineffective vertical scaling, and a single point of failure. The high-level cron execution architecture includes a Scheduled Job Conductor and a Job Queue. Slack also used a Vitess database table for deduplication and job tracking.
Table of contents
👋Goodbye low test coverage and slow QA cycles (Sponsored)The Role of Cron Jobs at SlackThe Issues with Cron JobsThe High-Level Cron Execution ArchitectureLatest articlesConclusionSPONSOR USSort: