3

Tried using Quartz scheduler, but it doesn't scale well. I need to schedule jobs dynamically for each user that runs after one month or after few months based on user input. Does anyone know which is the best option?

Kalika
  • 53
  • 4
  • 3
    The typical approach would be NOT to schedule separate jobs for each user but rather run to schedule a single job (running daily or hourly). It does the work for all users that are due on the execution date or time. The job uses controlled parallelism (e.g. 20 threads) to run efficiently. – Codo Jul 18 '20 at 19:30
  • 1
    And I hope you are not *just* scheduling the job because what happens if your server crashes? Are the jobs lost? You should do as the other comment already said: have one job that runs periodically and does whatever you want to do to all users that match a given criteria, – luk2302 Jul 18 '20 at 19:47
  • @Codo Using one job that runs periodically seems to be the way to do it. Will try that using Apache Flink as I'm already using Flink in my project. Thanks !! – Kalika Jul 19 '20 at 09:18

0 Answers0