Obsidian Feature Comparison/ Rising above the competition
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.
|Real-time schedule changes||Yes ||No ||No ||No|
|Real-time job configuration||Yes ||No ||No ||No|
|No-code, no-xml job configuration||Yes||No||No||No |
|Spring Framework support||Yes||Yes||No||Yes|
|Job event subscription/notification||Yes||No ||No ||No|
|Custom job listeners||No||Yes||Yes||No|
|Monitoring & management UI||Yes ||No||No||No|
|Ad-hoc job submission||Yes||No||No ||No|
|Job chaining||Yes ||No ||No ||No|
|Zero-configuration load sharing, clustering & failover||Yes||No ||No||No|
|Provides execution context/container||Yes ||No||No||Yes|
|Job execution host affinity||Yes||Not Available||Not Available||Not Available|
|Job scheduling & management REST API||Yes||No||No||No|
|Configurable job conflicts||Yes ||No||No||No|
|Scripting language support||Yes ||No||No||No|
|Custom calendar support||Yes||Yes||No||No|
|Cluster support||Yes ||Yes ||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.
- 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.
- 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.
- Allows for real-time modifications such as enabling and disabling jobs, runtime parameter addition, removal or modification, change the recovery mode, etc.
- At best, it still requires addition of annotations to your code base.
- Supports access thresholds corresponding to super users, standard operators and read-only access for developers and support staff.
- Conditional chaining based on output also supported.
- No out-of-the-box support. Requires additional setup and configuration.
- This is part of what enables Obsidian to allow such interactivity and visibility to the scheduling environment.
- Supports specifying execution priority of conflicted jobs.
- First node free, $499 CAD per additional nodes
- Requires configuration of JDBC-JobStore.