简体   繁体   English

Spring 批量与 Tivoli?

[英]Spring Batch vs Tivoli?

I was reading about Spring Batch and I read the below:我正在阅读有关 Spring Batch 的信息,并阅读了以下内容:

Spring Batch is not a scheduling framework. Spring Batch 不是调度框架。 There are many good enterprise schedulers (such as Quartz, Tivoli, Control-M, etc.) available in both the commercial and open source spaces.在商业和开源空间中都有许多优秀的企业调度程序(例如 Quartz、Tivoli、Control-M 等)可用。 It is intended to work in conjunction with a scheduler, not replace a scheduler.它旨在与调度程序一起工作,而不是取代调度程序。

Source: https://docs.spring.io/spring-batch/docs/current/reference/html/spring-batch-intro.html#springBatchBackground来源: https://docs.spring.io/spring-batch/docs/current/reference/html/spring-batch-intro.html#springBatchBackground

So what is the difference between Spring Batch and Tivoli ?那么Spring BatchTivoli之间有什么区别?

Spring Batch is mainly designed to provide a runtime for java batch workload. Spring Batch 主要旨在为 java 批处理工作负载提供运行时。

IBM Workload Scheduler (Tivoli) / HCL Workload Automation, like other schedulers, doesn't run the workload directly, but is used to triggers any kind of workload (jobs), including Spring Batch, on on-prem or hybrid and multi cloud environments, including Kubernetes. IBM Workload Scheduler (Tivoli) / HCL Workload Automation 与其他调度程序一样,不直接运行工作负载,而是用于在本地或混合和多云环境中触发任何类型的工作负载(作业),包括 Spring Batch ,包括 Kubernetes。

It can trigger jobs based on calendar, time, considering free/working day, complex runcycles (eg 3 working days before the end of each month).它可以基于日历、时间、考虑空闲/工作日、复杂的运行周期(例如每个月结束前的 3 个工作日)触发作业。

In addition it can trigger workload based on dependencies on other jobs, so that they can start as soon as the previous job (running on any other system) has completed successfully, or run jobs only if predecessor has completed with a specific RC or result.此外,它可以根据对其他作业的依赖性触发工作负载,以便它们可以在前一个作业(在任何其他系统上运行)成功完成后立即启动,或者仅在前一个作业已完成特定 RC 或结果时才运行作业。 Or you can use logic resources and limits to control how many jobs using the same machine or resource can run at the same time.或者,您可以使用逻辑资源和限制来控制使用同一机器或资源可以同时运行多少个作业。

It can be also used to trigger workload based on events, eg when a new file is uploaded.它还可以用于根据事件触发工作负载,例如上传新文件时。

In recent releases IBM Workload Scheduler / HCL Workload Automation also added built-in capabilities to transfer files.在最近的版本中,IBM Workload Scheduler / HCL Workload Automation 还添加了用于传输文件的内置功能。

IBM Workload Scheduler / HCL Workload Automation is also key to have a centralized monitoring and recovery of failures, to centralize security granting access to different teams only on their jobs, to have a centralized governance (eg auditing any change and recovery on jobs). IBM Workload Scheduler / HCL Workload Automation 也是集中监控和故障恢复、集中安全性以仅授予不同团队在其工作上的访问权限、进行集中式治理(例如审计任何更改和工作恢复)的关键。 It's also able to forecast the job durations and when every job will run, and generate alerts if they are running too long or if based on predecessors they are expected to miss their deadline.它还能够预测作业持续时间以及每个作业何时运行,并在它们运行时间过长或基于前任它们预计会错过最后期限时生成警报。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM