scheduler: new instance per run or long-lived actor?

[Александр Семибратов]

Hi

I want to implement task scheduler: supervisor actor and task-actor for each task. I see two approaches: 

1. Creating one instance of every actor-task in memory. Scheduler will send run-messages to this actors.

2. Creating new instance of task for every run. Scheduler will create new instance (via third actor) for every run and send run-message. Actor-task will be terminated after execution

Which approach is better?

What are the advantages and disadvantages of these approaches?

[Александр Семибратов]

For example

 

First approach 

https://gist.github.com/semibratov/d2968b7bd66198e636d64b9d0e35ec6b

Second approach

https://gist.github.com/semibratov/a0121fe73883a3b6216735ca20f75e63 

 

[wapgui]

Did you try this: https://github.com/enragedginger/akka-quartz-scheduler ?

[Александр Семибратов]

No. Akka scheduler suits my needs.

пятница, 23 февраля 2018 г., 13:01:46 UTC+4 пользователь wapgui написал:

[Александр Семибратов]

Share your opinions, please :-)

пятница, 23 февраля 2018 г., 21:51:57 UTC+4 пользователь Александр Семибратов написал:

[wapgui]

In build.sbt:

"com.enragedginger" %% "akka-quartz-scheduler" % akkaQuartz.version

In application.conf:

akka {
  quartz {

    defaultTimezone = "Europe/Berlin"
    schedules {
      ReloadDIY {
        description ="Reload content every day"
        expression = "0 0/5 * * * ?"
      }
    }
  }
}

In code:

val scheduler = QuartzSchedulerExtension(actorSystem)

scheduler.schedule("Reload", actorSystem.actorOf(Props[ReloadActor]), "Reload")

That's all and works fine for me. It was used with akka 2.4, maybe now the akka internal scheduler is easier to use.