Service pool architecture for multitenant services to support canary release

A method comprising:

• at an enterprise canary release server comprising at least one processor, memory, and a communication interface:
• creating a plurality of types of service pools in a cloud-based system that supports a plurality of tenants, wherein each service pool comprises a plurality of microservices that share a common functionality, wherein a virtual site is provisioned with a service pool from each type of service pools, and wherein the microservices assigned for the virtual site are associated with a single-tenant database;
• receiving, via the communication interface, a request to perform a canary release for a new version of software, wherein the request identifies a first microservice out of the plurality of microservices in a first service pool of a first type of service pools, wherein the first microservice is configured to communicate with a second microservice in a second service pool of a second type of service pools;
• dynamically assigning a first number of microservices from the plurality of microservices in the first service pool and a second number of microservices from the plurality of microservices in the second service pool to service the virtual site based on a variation of loads in the first service pool and the second service pool;
• instantiating a new microservice that hosts the new version of the software in the first service pool;
• enabling data plane connectivity between the new microservice and the second microservice;
• and
• disabling data plane connectivity between the first microservice and the second microservice.

One or more non-transitory computer-readable media storing instructions that, when executed by a computing platform comprising at least one processor, memory, and a communication interface, cause the computing platform to:

• create a plurality of types of service pools in a cloud-based system that supports a plurality of tenants, wherein each service pool comprises a plurality of microservices that share a common functionality, wherein a virtual site is provisioned with a service pool from each type of service pools, and wherein the microservices assigned for the virtual site are associated with a single-tenant database;
• receive, via the communication interface, a request to perform a canary release for a new version of software, wherein the request identifies a first microservice out of the plurality of microservices in a first service pool of a first type of service pools, wherein the first microservice is configured to communicate with a second microservice in a second service pool of a second type of service pools;
• dynamically assign a first number of microservices from the plurality of microservices in the first service pool and a second number of microservices from the plurality of microservices in the second service pool to service the virtual site based on a variation of loads in the first service pool and the second service pool;
• instantiate a new microservice that hosts the new version of the software in the first service pool;
• enable data plane connectivity between the new microservice and the second microservice;
• and
• disable data plane connectivity between the first microservice and the second microservice.