When scheduling jobs within BeyondCron, group properties make setting a familiar, and consistent, environment a breeze. See a familiar environment.
Month calendars and schedules, make scheduling a day at the races a sure bet. See a day at the races.
Using date schedules makes executing infrequent jobs a breeze. See once in a blue moon.
Ensuring that jobs aren’t missed when daylight savings starts is simple with trigger jobs. See nothing missed.
At its simplest, BeyondCron is a client-server implementation of the cron daemon, in which all jobs are defined centrally rather than individually on each server.
Crontabs can be directly imported into BeyondCron, enabling quick import of existing cron environments into BeyondCron.
In a standard cron environment, jobs need to be configured and controlled independently for every server and every user. Whereas BeyondCron maintains and controls jobs within an environment centrally.
The dashboard within BeyondCron allows jobs (and calendars) to be created, controlled and visualised from a single location. Not only does it support drag-and-drop for quickly creating job flows, but it updates in realtime as jobs execute.
BeyondCron supports scheduling functionality that goes above and beyond what is available using cron.
Rather than having to define a start time for every job, jobs can be organised into job flows, with each job automatically executing upon completion of the previous job in the flow. See schedules, triggers & conditions.
Reduced execution times
Because jobs within a flow can run one after another, rather than being scheduled individually, with sufficient time between them, overall run times can be reduced.
Since only the first job in a flow needs to be scheduled, following jobs will not be missed, or worse executed, when the previous job has not completed, or fails.
Calendars can be associated with jobs such that they do, or do not execute on holidays. Calendars can be defined in Outlook/Mac Mail and imported into BeyondCron via subscription, or a file.
Jobs can be scheduled based upon events within a calendar, providing separation between job definition and schedule, as well as allowing jobs to be safely rescheduled on an ad hoc basis. See calendar scheduling.
As well as executing commands, jobs can also execute SQL, schedule containers, call webhooks, send emails, or simply trigger other jobs with an option delay.
Along with cron, BeyondCron supports date, daily, monthly, repeat, calendar & solar schedule types, simplifying the creation of standard schedules, as well as providing new scheduling options that would be impossible to define using cron. See job schedules.
Group properties make setting a familiar, and consistent, environment a breeze. See a familiar environment.
Job flows can be built using wildcards. This can used for example, to send an email when any job fails. See email jobs & wildcards.
BeyondCron makes it easy to insert dates into jobs. Not only can dates be formatted to meet any requirement, they can also be adjusted forwards or backwards. See let's make a date.
Easy to read times
BeyondCron uses easy to read times, such as “Today 09:17:00”, instead of "09/02/2016 09:17:00”, for dates between yesterday and the next 7 days. See easy to read times.
All jobs have an associated timezone, ensuring that jobs execute as expected, irrespective of server location. See timezones.
Into the enterprise
Moving beyond cron, BeyondCron offers functionality which until now has only been available on enterprise class schedulers…along with enterprise levels of complexity and pricing.
By default BeyondCron executes jobs over SSH, eliminating the need to install and maintain agents.
BeyondCron provides standard read/execute/write access controls on jobs and calendars. It also provides controls on users & hosts, ensuring that developers cannot schedule commands as root, or on production servers. See control built in.
All job, calendar and user definitions are logged using Git for recovery, rollback and auditing. See what changed?
BeyondCron servers automatically form a cluster when started, providing high availability. Unlike some application clusters, BeyondCron clusters are masterless, with automatic recovery on node failure. See high availability.
When a server is added to a BeyondCron cluster, job scheduling is automatically re/distributed across all servers, ensuring that BeyondCron does not become CPU or memory constrained as your environment grows. See horizontal scaling.
BeyondCron supports container scheduling within a Mesos cluster.
Subscribe to BeyondCron news
Subscribe to BeyondCron news
The latest BeyondCron news sent straight to your inbox, or follow us in Twitter
Your request has been received by BeyondCron, and we will reply shortly.
You have joined the BeyondCron news email list.