Did you ever dream, your background workload would just scale just as easily as your REST endpoints? Enter planlagt. A distributed work scheduler, which automagically distributes re-occurring work (read: cron jobs) across all running instances of your service. Configure once, scale at your leisure. Automatic fail-over and retry logic for peaceful nights. So what is this talk about? I will guide you trough my headspace of how planlagt came to be, and which problems it solves. This also includes talking about planlagt's backbone, [synchronized cron task](https://github.com/kernle32dll/synchr.... If time permits, I will also give an outlook for the future of both projects. Both projects currently work with Redis, but can be extended in the future.