Obsidian: Difference between revisions

From Obsidian Scheduler
Jump to navigationJump to search
No edit summary
Line 13: Line 13:
= Basic Features =
= Basic Features =
* Cron-style patterns are used for job scheduling.
* Cron-style patterns are used for job scheduling.
* Fully-featured administration and monitoring web application.
* Notifications and logging of scheduler events and failures.
* Notifications and logging of scheduler events and failures.
* Job configuration can be changed at any time - no restarts or rebuilds.
* Job configuration can be changed at any time - no restarts or rebuilds.

Revision as of 01:29, 20 February 2011

Espresso is Carfey Software's Java-based scheduling tool.

It takes the power and expressiveness of Cron and combines it with enterprise-class features like load-balancing, failover and conflict prioritization.

Overview

Espresso replaces tools like Cron and Quartz by taking the basic features in a scheduler and adding full management capabilities, workflow, conflict resolution, native load-balancing and failover.

It is a Java-based application, and can be run standalone or embedded within a Java process.

Jobs can be configured and managed from within the administration console, and allow cron-style job patterns, schedule windows and advanced parameterization.

Basic Features

  • Cron-style patterns are used for job scheduling.
  • Fully-featured administration and monitoring web application.
  • Notifications and logging of scheduler events and failures.
  • Job configuration can be changed at any time - no restarts or rebuilds.
  • One simple Java interface to implement to make a job compatible with Espresso.
  • Schedule windows allow you to have future schedule changes (disable a job or change its runtime schedule).
  • Job parameterization allows for multiple instances of jobs with different configurations.

Enterprise Features

  • Espresso instances automatically cooperate to perform load-balancing and provide failover.
  • Even with a single node licence, a second node may be running in standby to automatically pick up if its peer dies.
  • Job conflicts can be configured to provide automatic job prioritization and conflict resolution.
  • Jobs may be chained to others based on various conditions to provide job workflow support.
  • Floating node licences allow flexibility and choice to users.