Where will the conversation continue?
email
Some local job schedulers are available at Stanford applications, such as Oracle, Informatica, etc. However, when dealing with cross systems dependencies, local job schedulers cannot manage data or workflow dependencies. Enterprise job scheduler is needed if we have to deal with hybrid systems (on-prem, in Cloud) running on different platforms and on different networks segments.
Notes
Basic features expected of enterprise job scheduler software include:
- interfaces which help to define workflows and/or job dependencies
- automatic submission of executions
- interfaces to monitor the executions
- priorities and/or queues to control the execution order of unrelated jobs
- internal calendar to manage its own schedules (holidays, maintenance windows, etc)
- runtime logs and reporting capabilities
Some local job schedulers are currently available at Stanford applications, such as Oracle, Informatica, etc. However, when dealing with cross systems dependencies, local job schedulers cannot manage data or workflow dependencies.
Schools are starting to adopt more cloud based applications, the need of enterprise job scheduler is getting more attention. Especially data integration teams deal with multiple upstream, hybrid systems (on-prem, in Cloud) running on different platforms and on different networks segments.
