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?
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.
2,193Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
