Isolated environment provisioning in service mesh-based microservices systems

A method, comprising:

• receiving, by a system comprising at least one processor, a changeset for an updated microservice and an identifier of a user account, wherein the updated microservice is representative of an update to a current version of a microservice that is deployed to a service mesh;
• deploying, by the system, the updated microservice to the service mesh based on the changeset;
• updating, by the system, routing rules for the service mesh to indicate that any traffic in the service mesh that is associated with the user account and that is directed to the current version of the microservice is to be routed to the updated microservice;
• and
• in response to receiving traffic that is associated with the user account and that is directed to the current version of the microservice, routing, by the system, the traffic to the updated microservice while foregoing routing the traffic to the current version of the microservice, wherein the traffic is routed through microservices that comprises the updated microservice, the traffic being routed comprising,
• extracting, by the system, the identifier of the user account from a first call that corresponds to the traffic that is directed to a first microservice of the microservices in a call chain to produce an extracted identifier of the user account;
• storing, by the system, the identifier of the user account in a token that is passed between microservices of the call chain that corresponds to the traffic;
• and
• inserting, by the system, the extracted identifier of the user account into a second call that corresponds to the traffic, and that is originated by the first microservice and destined for a second microservice of the microservices in the call chain.

A non-transitory computer-readable medium comprising instructions that, in response to execution, cause a system comprising at least one processor to perform operations, comprising:

• based on receiving an identifier of a user account and a changeset applicable to generate an updated microservice relative to a current version of a microservice that is deployed to a service mesh, deploying the updated microservice to the service mesh;
• updating routing rules for the service mesh to indicate that any portions of traffic in the service mesh that are associated with the user account and that are directed to the current version of the microservice is to be routed to the updated microservice;
• in response to receiving first traffic of the traffic, wherein the first traffic is determined to be associated with the user account and determined to be directed to the current version of the microservice, routing the first traffic to the updated microservice instead of routing the first traffic to the current version of the microservice, wherein the first traffic is routed through microservices that comprises the updated microservice, the first traffic being routed comprising,
• extracting the identifier of the user account from a first call that corresponds to the traffic that is directed to a first microservice of the microservices in a call chain to produce an extracted identifier of the user account;
• storing, by the system, the identifier of the user account in a token that is passed between microservices of the call chain that corresponds to the traffic;
• and
• inserting the extracted identifier of the user account into a second call that corresponds to the first traffic, and that is originated by the first microservice and destined for a second microservice of the microservices in the call chain.