Recommended actor versioning pattern
❓type: question
What is the recommended pattern for handling actor's code and state mismatch after releasing a new version of my app (the new code produces different state)? If I understand correctly the state is always persisted, but the code that interacts with the state can change when actor upgrades it's version. Is doing a state migration onWake the correct solution here?
For my usecase I don't really need actor's state - I could just use vars, because the data will be persisted into a separate database. Doing this would keep the "state"<->code in sync after a release, but it looks like a total antipattern.
I'm totally new to actors and DOs, so I'm sorry if I'm missing something totally obvious. I need some guidance on this issue
For my usecase I don't really need actor's state - I could just use vars, because the data will be persisted into a separate database. Doing this would keep the "state"<->code in sync after a release, but it looks like a total antipattern.
I'm totally new to actors and DOs, so I'm sorry if I'm missing something totally obvious. I need some guidance on this issue
Build and scale stateful backends. Rivet Actors is a library for long-lived processes with durable state, realtime, and scalability. Easily self-hostable and works with your infrastructure.
1,419Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
