Quartz Scheduler - RAM和JDBC Job store之间的区别是什么 [英] Quartz Scheduler - What is the diff between RAM and JDBC Job store

问题描述

我想在我的应用程序中使用Quartz Scheduler框架。我遇到了两种类型的JobStores：

I want to use Quartz Scheduler framework in my application. I came across two types of JobStores:

1）RAM Job Store

1) RAM Job Store

2）JDBC Job store。

2) JDBC Job store.

我想知道在哪种情况下我必须使用哪个求职店。他们之间的利弊是什么。

I am wondering in which case I have to use which job store. And what is the pros and cons between them.

对此我有任何想法对我很有帮助，我很感激。

Any thoughts on this is really helpful for me and I appreciate it.

推荐答案

JDBC作业存储在数据库中保存有关已触发的触发器和作业的信息，因此：

JDBC job store saves information about fired triggers and jobs in the database, thus:

• 如果应用程序停止时触发器被激活（这取决于选择的失火指令），它不会失去激活

• it won't lose firings if application was down when trigger was suppose to fire (this depends on chosen misfire instruction)

你可以集群您的调度程序，其中每个节点使用相同的数据库

you can cluster your scheduler, where each node uses the same database

JDBC作业存储相当慢

JDBC job store is considerably slower

RAM作业存储仅适用于非集群应用程序，其中失去解雇并不是什么大问题。它也快得多。如果你想使用带有RAM作业存储的Quartz，很可能你根本就不需要Quartz。 Spring和EJB都提供了运行定期作业的机制，包括时间和基于CRON。

RAM job store is applicable only in non-clustered application where loosing a firing is not a big deal. It's also much faster. If you want to use Quartz with RAM job store, most likely you don't need Quartz at all. Both Spring and EJB provide mechanisms to run periodic jobs, both time and CRON based.

这篇关于Quartz Scheduler - RAM和JDBC Job store之间的区别是什么的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！