Zero down time upgrade for a multi-tenant identity and data security management cloud service

A method of providing cloud-based identity and access management, comprising:

• receiving a request for performing an identity management service, wherein the request identifies the identity management service and a current version of a microservice configured to perform the identity management service, wherein the current version of the microservice is in a first stateless middle tier in a first topology that includes a first web tier configured to route the request;
• performing the identity management service by the current version of the microservice using tenant data stored in a database;
• determining an upgrade to be applied to the microservice;
• deploying a second topology that implements the upgrade, wherein the second topology includes a second stateless middle tier including a new version of the microservice, wherein the second topology further includes a second web tier configured to route requests in the second topology;
• testing the new version of the microservice in the second topology using test data stored in the database;
• promoting the second topology;
• and
• draining and shutting down the first topology.

A system comprising:

• a processor;
• and
• a non-transitory computer readable medium having instructions stored thereon that, when executed by the processor, cause the processor to provide cloud-based identity and access management, the providing comprising:
• receiving a request for performing an identity management service, wherein the request identifies the identity management service and a current version of a microservice configured to perform the identity management service, wherein the current version of the microservice is in a first stateless middle tier in a first topology that includes a first web tier configured to route the request;
• performing the identity management service by the current version of the microservice using tenant data stored in a database;
• determining an upgrade to be applied to the microservice;
• deploying a second topology that implements the upgrade, wherein the second topology includes a second stateless middle tier including a new version of the microservice, wherein the second topology further includes a second web tier configured to route requests in the second topology;
• testing the new version of the microservice in the second topology using test data stored in the database;
• promoting the second topology;
• and
• draining and shutting down the first topology.