Hi all! I'm wondering if Akka is a good fit for my use case and about best practices. I'm going through the tutorial right now. I'm working on a distributed ETL and scheduling system as a side project. Akka seems like a great fit.

Last question, and I might just need to finish the tutorial to find this one out, but what is the best way to store workflows (ex. for ETL) in a central repo and have the worker nodes load them up and start execution according to schedules?

Is that implemented in Akka, or is that something I would need to write?

I'm trying to understand what happens to child actors. For instance, in lesson 1.4 "Add TailActor as a child of TailCoordinatorActor", inside OnReceive() there is : Context.ActorOf(Props.Create(() => new TailActor(msg.ReporterActor, msg.FilePath)));. Does this actor that is created need to be stopped or disposed somehow?