Live Chat Software

Obsidian Feature Comparison/ Rising above the competition

Comparing Features

We believe that Obsidian Scheduler is the best choice for most scheduling needs. Obsidian is designed for both simple or complex scheduling requirements, so see for yourself how it stacks up against the competition.

Feature
Obsidian
Quartz
cron4j
Spring
Real-time schedule changes Yes [1] No [2] No [2] No
Real-time job configuration Yes [3] No [2] No [2] No
No-code, no-xml job configuration Yes No No No [4]
Spring Framework support Yes Yes No Yes
Job event subscription/notification Yes No [2] No [2] No
Custom job listeners No Yes Yes No
Monitoring & management UI Yes [5] No No No
Embeddable Yes Yes Yes Yes
Ad-hoc job submission Yes No No [2] No
Job chaining Yes [6] No [2] No [2] No
Zero-configuration load sharing, clustering & failover Yes No [7] No No
Provides execution context/container Yes [8] No No Yes
Job execution host affinity Yes Not Available Not Available Not Available
Scheduling precision Minute Second Minute Second
Job scheduling & management REST API Yes No No No
Configurable job conflicts Yes [9] No No No
Java jobs Yes Yes Yes Yes
Scripting language support Yes [10] No No No
Custom calendar support Yes Yes No No
Cluster support Yes [11] Yes [12] Not Available Not Available

In addition to the features listed above, we are confident that Obsidian excels at even more subjective measures including simplicity of job development, ramp-up time, reliability and ease-of-use.

Reference

  1. With Obsidian you can even “schedule” a runtime schedule change. For example, change a job currently running on the hour to begin running at half past the hour beginning tomorrow or next week.
  2. Library does not support this out of the box. Additional code is required to interact with the API, and an execution context would be required to do so.
  3. Allows for real-time modifications such as enabling and disabling jobs, runtime parameter addition, removal or modification, change the recovery mode, etc.
  4. At best, it still requires addition of annotations to your code base.
  5. Supports access thresholds corresponding to super users, standard operators and read-only access for developers and support staff.
  6. Conditional chaining based on output also supported.
  7. No out-of-the-box support. Requires additional setup and configuration.
  8. This is part of what enables Obsidian to allow such interactivity and visibility to the scheduling environment.
  9. Supports specifying execution priority of conflicted jobs.
  10. Groovy, Python, Javascript and Beanshell natively supported.
  11. First node free, $399 CAD per additional nodes
  12. Requires configuration of JDBC-JobStore.
Copyright © 2011-2013 Carfey Software. All rights reserved.