Abstract: In an example embodiment, to improve performance, a solution is provided that removes the bottleneck associated with a single events table. Specifically, the solution provides for three events tables rather than one table. Two of the three tables are domain event outbox tables that are parallel and equivalent to each other. The third table is a domain event indication table, which records which of the domain event outbox tables is in a serve mode versus a maintain mode. At any point in time, one of the two domain event outbox tables is in serve mode while the other is in maintain mode. Serve mode is used for event insert, update, and query, while maintain mode is used for event purge.

Abstract: System computing resources are dynamically managed by a resource management layer together with resource server pool. A group monitor collects data of server operation (e.g., CPU usage, memory consumption, queue size) in a particular group (e.g., customer-facing servers, job servers). The group monitor: calculates a weighted score for each server, sorts the scores of each server, maintains a sequence of scores, and periodically reports the score list to a resource manager. When an incoming request is directed to a particular server group, the group monitor redirects the request to a lowest-scoring server, and recalculates/sorts the score list. The resource manager monitors and throttles the servers in each group. Where servers in a group are experiencing high workload, the manager adds to the group server(s) from the resource pool. Conversely, where server group members are experiencing a low workload, the manager removes the lowest scoring server(s) to the resource pool.

Abstract: System computing resources are dynamically managed by a resource management layer together with resource server pool. A group monitor collects data of server operation (e.g., CPU usage, memory consumption, queue size) in a particular group (e.g., customer-facing servers, job servers). The group monitor: calculates a weighted score for each server, sorts the scores of each server, maintains a sequence of scores, and periodically reports the score list to a resource manager. When an incoming request is directed to a particular server group, the group monitor redirects the request to a lowest-scoring server, and recalculates/sorts the score list. The resource manager monitors and throttles the servers in each group. Where servers in a group are experiencing high workload, the manager adds to the group server(s) from the resource pool. Conversely, where server group members are experiencing a low workload, the manager removes the lowest scoring server(s) to the resource pool.

Abstract: A cloud computing system receives a plurality of requests originating from a plurality of tenants. Thereafter, a load balancer forming part of the cloud computing system dispatches each request to one of a plurality of groups of servers based on a group mapping table configured to optimize a cache hit ratio. Each group of servers includes a plurality of servers dispatching each request to one of the plurality of servers within each group of servers. The cloud computing system provides responses to the requests to the respective tenants as generated by the respective servers within the respective groups of servers. The group mapping table can be generated by monitoring historical request statistics for each of the tenants, monitoring current resource consumption by the plurality of groups of servers when handling requests from the tenants, and associating each tenant with one of the groups of servers based on such monitoring.