Reactor persistence and user tasks
I have a fairly involved saga I want to implement that I have currently as adhoc liveviews but that I want to make a bit more robust. Reactor seems fairly good for this (although I don't really need rollbacks). This saga includes both automated tasks (call some APIs, generate some data) and user-led steps, where the user has to interact with some stuff. Is this something that reactor would be good for? Would you create a model that stores the current step in the DB and then restarts from the next steps? Have you done similar things in the past? What would be the best practices for that?
1 Reply
I asked something similar ðŸ¤
I’ve definitely found that lots of small reactors is the way to go because you can compose them.You could store the reactor state, get it somehow and continue the same flow, it is possible. But I think same should be achievable with a simpler approach of making multiple small reactors 🤔 don't know about the user interactive part, my first thought is that that doesn't need a reactor :thinkies: I'm curious what will the sag(a)es say 🙇