Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

Hello,

We are currently using jdbcjobstore for quartz scheduler. This is working fine.
Now there is a requirement to move away from db so just exploring what are other options. We certainly can't use RAM store as we want persistence.

We want to develop a custom job store. lucene could be used for persistence since its being used for some other storage purpose in the project apart from search.

What are the starting points for developing custom jobstore? Any pointers would be helpful.

Thanks,
Ram

You can use Trerracotta Jobstore to persist your data.
TerracottaJobStore can be ran clustered or non-clustered, and in either case provides a storage medium for your job data that is persistent between application restarts, because the data is stored in the Terracotta server. It's performance is much better than using a database via JDBCJobStore (about an order of magnitude better), but fairly slower than RAMJobStore.

http://quartz-scheduler.org/documentation/quartz-2.x/tutorials/tutorial-lesson-09

Cheers!!!!

I have seen Terracotta Jobstore link which looks like a custom jobstore.

Here we don't want to add more dependencies to the project so have the thought of adding a custom jobstore.

Thanks,
Ram