Job Schedulers were the norm for enterprises internal and especially external long-running and business-critical processes. Processes executed by job schedulers are also often termed batch processes and fell out of fashion when near-real time and real-time processing became possible due to web service exposed, queue-based services.
While real-time processing has succeeded in removing some use of job schedulers, all operating systems, most database management systems, and some middleware provide implementers job schedulers. Job schedulers act, in this way, as a recurring triggering point for execution of activities when the driving force is the passage of time, not user-interaction.
Job schedulers provided by operating systems and database management systems are bound to a single machine so do not provide an apparent means to distribute execution across a set of machines. Additionally, activity execution via traditional job schedulers is bound to the available commands of the execution environment, ie a Bash script via cron or SQL command via SQL Server's job scheduler. Job schedulers also do not provide an apparent means to schedule point-in-time execution. And job schedulers do not provide for programmatic scheduling, an API.
The Open Scheduled Task Engine extends the capabilities of traditional job schedulers, making distributed execution and point-in-time scheduling ostensible and available for programmatic access via a RESTful API. The Open Scheduled Task Engine is open in that it does not execute processes; processes are distributed and executed by sending HTTP requests to services.
No comments:
Post a Comment