Live updates of stateful components

An apparatus for managing software updates, comprising:

• a processor;
• memory coupled with the processor;
• and
• instructions stored in the memory and executable by the processor to cause the apparatus to:
• execute a first set of requests at a first version of a software component deployed to a container, wherein the software component comprises a stateful component, and wherein executing the first set of requests changes an in-memory state of the software component managed by the container based at least in part on the software component comprising the stateful component;
• receive, from a user device, a software patch comprising a second version of the software component;
• deploy the second version of the software component to the container based at least in part on the software patch and concurrent with executing at least a first portion of the first set of requests at the first version of the software component;
• route a second set of requests to the second version of the software component based at least in part on the deploying;
• and
• update, at the container, the in-memory state of the software component based at least in part on the first version of the software component and the second version of the software component.

A non-transitory computer-readable medium storing code for managing software updates, the code comprising instructions executable by a processor to:

• execute a first set of requests at a first version of a software component deployed to a container, wherein the software component comprises a stateful component, and wherein executing the first set of requests changes in-memory state of the software component managed by the container based at least in part on the software component comprising the stateful component;
• receive, from a user device, a software patch comprising a second version of the software component;
• deploy the second version of the software component to the container based at least in part on the software patch and concurrent with executing at least a first portion of the first set of requests at the first version of the software component;
• route a second set of requests to the second version of the software component based at least in part on the deploying;
• and
• update, at the container, the in-memory state of the software component based at least in part on the first version of the software component and the second version of the software component.