Current fetiche-engine design is hampering us

[keltia]

The current design of Engine is blocking us from using it fully inside fetiched and it knows too much, some of its data is not at the right place. State management is included, some paths are complicated to override and some of it should move into separate actors.

[keltia]

We should have a separate storage actor, probably a statistics one and Config should be handling more.

[keltia]

Separating into different actors is needed but not enough, the current Engine does really too many things. BTW storage actor is there BTW. We are hitting the limit of the current design which is an hybrid between library included in an executable like acutectl and just a part of fetiched. We may have to fork the entire fetiche-engine in the engine actor.

[keltia]

fetiche-engine has been forked into acutectl for now and fetiched will incorporate the core of it (removing state, storage, etc. stuff). Fork done in f2d88ff.
Main take away: fetiched is engine at the core and all the actors are peripheral services. fetiche-sources might end up here as well.

[keltia]

As of 3946751 , branch has been merged into develop so fetiched has a working trimmed-down version of Engine without storage & state management.