A Meteor package providing a cron system with synchronization across multiple server processes.
Synced Cron is a Meteor package that provides a simple cron system for scheduling and executing recurring tasks within Meteor applications. It solves the problem of duplicate job execution in distributed deployments by using MongoDB to coordinate between multiple server processes, ensuring each scheduled job runs only once across the cluster.
Meteor developers who need to run scheduled background jobs (like data aggregation, report generation, or cleanup tasks) in a multi-server deployment environment where process synchronization is required.
Developers choose Synced Cron over generic Node.js cron solutions because it offers built-in synchronization for Meteor apps, preventing duplicate executions without external services, and integrates seamlessly with Meteor's ecosystem and MongoDB.
A simple cron system for Meteor. It supports syncronizing jobs between multiple processes.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses a MongoDB collection to coordinate job execution across multiple server processes, ensuring each scheduled job runs only once per interval, as explicitly described in the README for distributed deployments.
Leverages the Later.js library for expressive scheduling via human-readable text or parser objects, allowing complex cron patterns without manual date calculations, as shown in the API examples.
Automatically maintains a detailed history of job executions with timestamps and results in a configurable MongoDB collection, useful for debugging and auditing, with options for TTL management.
Designed specifically for Meteor, it integrates seamlessly with Meteor's build system and conventions, reducing setup overhead and providing a native solution for scheduled tasks.
Exclusively tied to the Meteor framework, making it unusable for any other JavaScript or Node.js environment, which severely limits its applicability and portability.
As admitted in the Caveats section, it may fail on shared hosting providers that shut down idle app instances, such as Heroku's free dyno tier, leading to unreliable job execution.
Heavily relies on MongoDB for synchronization and logging, introducing a single point of failure and requiring manual index management for TTL, as noted in the configuration warnings.
Lacks built-in support for job retries, priority handling, or a graphical monitoring interface, which are common in more robust job scheduling systems like Agenda or Bull.