Use Cases

Job Scheduling and Batch Tasks

The Problem: Tool Sprawl and Knowledge Silos

Every enterprise has batch workloads scheduled to run unattended or on-demand to support business operations. Sometimes these are maintenance tasks. Other times these are batch data processing or analytics jobs.

When it comes to tools, you previously had to choose between a sprawl of individual schedulers (Cron, Task Scheduler, etc.) or the friction of monolithic enterprise schedulers (Tidal, Control-M, Autosys, etc.) and specialist ETL tools.

 

comic_8-01

 

With the individual scheduling tools, you have to contend with the management overhead of multiple low-level local configurations.

With the centralized enterprise schedulers and ETL tools, you get overly complicated implementations requiring specialized knowledge and eye-popping budgets.

 

comic_9-01

 

To further complicate matters, neither type of tool was designed for self-service and modern DevOps-inspired ways of working.

Without self-service capabilities, it is difficult to avoid the bottlenecks and the delays that come from only a few people being able to manage to create and maintaining batch tasks.

 

comic_7-01

 

The Rundeck Solution

Rundeck makes it simple and easy to setup self-service job scheduling. Rundeck provides a centralized solution that is:

  1. Lightweight to setup — Reuse your existing tools and scripts, add new ones with ease
  2. Easy to manage — Doesn’t involve new skills or languages, which makes Rundeck a trusted part of your infrastructure the whole organization can use.
  3. Highly cost-effective — Simple licensing model, low-cost implementation, and the ability to reuse your investment for multiple use cases.

More details:

  • Quickly create workflow jobs that span your existing tools, scripts, system commands, and API calls
  • Leverage the existing automation tools and languages that your teams already know
  • Define the schedule for each job (workflow)
  • Make your jobs safer to run by leveraging Rundeck's "guardrails" features like error-handling, fork and merge style workflow features, conditionals, data passing between steps, notifications, and more
  • Use Rundeck's built-in access control features to define the fine-grained permissions (use your existing AD/LDAP or SSO for authentication) determining who can create, modify, or view what jobs.
  • Rundeck's simplicity and low entry barrier means that you can easily allow any number of your colleagues to define and manage operations tasks, analytics jobs, or any other scheduled activity
  • Use read-only access combined with logging and notification features to give broad visibility into provisioning activity across your organization. 
  • Rundeck's resource model learns details about your environment from multiple sources (Rundeck plugin points), so your automation can be parameterized and kept up to date

 

ROI Tips

  • If you are consolidating multiple local schedulers, baseline the overhead costs of managing individual schedulers. Be sure to consider both the maintenance cost (labor to setup infrastructure  and maintain) and cost of issues that arise from schedule collisions, missing configurations, or other errors. 
  • If you are avoiding enterprise schedulers or ETL workflow tools, baseline the overhead costs of having a complicated and expensive siloed solution. Be sure to consider the cost of having to train and maintain knowledge of a complicated specialized tool and also consider the expensive per job based licensing costs.
More about Rundeck’s ROI