Originally reported by: Jan Pipek (Bitbucket: janpipek, GitHub: janpipek)
I don't like the way Chain (in a naive way) and MapReduce (in a more sophisticated way) create actors and use schedulers. My opinion is that no actor should ever know what a scheduler is.
We should think about another implementation that would allow dynamic creation of actors. I suggest that we create something like "temporary actors" which will be returned by the main actor (@decorated or inheriting DynamicActor) and reused in the workflow scheduler and later deleted.
coobas
commented
6 years ago
Originally reported by: Jan Pipek (Bitbucket: janpipek, GitHub: janpipek)
I don't like the way Chain (in a naive way) and MapReduce (in a more sophisticated way) create actors and use schedulers. My opinion is that no actor should ever know what a scheduler is.
We should think about another implementation that would allow dynamic creation of actors. I suggest that we create something like "temporary actors" which will be returned by the main actor (@decorated or inheriting DynamicActor) and reused in the workflow scheduler and later deleted.