RAMJobStore is the simplest JobStore to use. It is also offers the best performance (in terms of CPU time).

A RAMJobStore, as its name indicates, keeps all of its data in RAM. This is why it's lightning-fast and also why it is simple to configure.

The drawback to using RAMJobStore is that when your application ends (or crashes), all of the scheduling information is lost. Therefore, a RAMJobStore cannot honor the setting of "non-volatility" on jobs and triggers. For some applications this is acceptable, or even the desired behavior, but for other applications, this may be disastrous.

To use RAMJobStore (and assuming you're using StdSchedulerFactory) simply set the org.quartz.jobStore.class property to org.quartz.simpl.RAMJobStore as illustrated in the example below:

There are no other settings you need to worry about.