Instead of worrying about migrating user's coroutines across upgrades you just did the "Erlang trick" and moved them over to the new deployments.
I'd like to hear how this works in detail. Suppose a user is exercising a multi-request handler, say pagination of personalized results.
At what point do you kill the coroutine and let the next request start a new handler in the new, upgraded process? What about state that the coroutine may have that hasn't been persisted anywhere else?
I'd like to hear how this works in detail. Suppose a user is exercising a multi-request handler, say pagination of personalized results.
At what point do you kill the coroutine and let the next request start a new handler in the new, upgraded process? What about state that the coroutine may have that hasn't been persisted anywhere else?