Metadata-driven dynamic load balancing in multi-tenant systems

• US 10,091,282 B2
• Filed: 06/12/2013
• Issued: 10/02/2018
• Est. Priority Date: 06/12/2013
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Said, Bare, Jentsch, Frank, Brunswig, Frank
• Primary Examiner(s): Dollinger, Tonia L
• Assistant Examiner(s): Sayoc, Kristoffer L S
• Application Number:
  US13/916,286
• Publication Number:
  US 20140372550A1
• Time in Patent Office: 1,938 Days
• Field of Search: 709213, 709203, 709224
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30

Abstract

The disclosure generally describes computer-implemented methods, computer program products, and systems for providing metadata-driven dynamic load balancing in multi-tenant systems. A computer-implemented method includes: identifying a request related to a model-based application executing in a multi-tenant system associated with a plurality of application servers and identifying at least one object in the model-based application associated with the request. At least one application server is identified as associated with a locally-cached version of a runtime version of the identified object, and a determination of a particular one of the identified application servers to send the identified request for processing is based on a combination of the availability of a locally-cached version of the runtime version at the particular application server and the server'"'"'s processing load. The request is then sent to the determined application server for processing.

Claims

1. A computer-implemented method, the method executed by one or more processors, the method comprising:

identifying, at a load balancer, a request related to a model-based application executing in a multi-tenant system, wherein the multi-tenant system associated with a plurality of application servers, and wherein the load balancer manages routing of identified requests related to the model-based application to particular application servers in the multi-tenant system;

identifying, by the load balancer, at least one object in the model-based application associated with the identified request, wherein identifying the at least one object includes accessing a metadata repository associated with the model-based application to identify one or more design time objects associated with the identified request;

accessing, by the load balancer, a multi-tenant cache map storing information defining a current status of local caches of each of the plurality of application servers in the multi-tenant system maintained by the load balancer, wherein the multi-tenant cache map collects local cache information from each of the plurality of application servers in the multi-tenant system and identifies at least the locally-cached runtime versions of objects available in the corresponding local cache of the particular application servers;

identifying, by the load balancer using the multi-tenant cache map, at least two application servers from the plurality of application servers based on a determination that each of the at least two application servers includes, at a time the request is identified, a locally-cached version of at least one runtime version of the at least one identified object in the model-based application based on the current status of the local caches of the at least two application server as defined in the multi-tenant cache map; and

in response to identifying the at least two application servers, determining, by the load balancer, a particular application server from the at least two application servers to send the identified request for processing based at least in part on a combination of the locally-cached version of the at least one runtime version being available at the particular application server and the relative processing load of the particular application server as compared to the other application servers in the at least two identified application servers; and

sending, by the load balancer, the identified request to the determined particular application server for processing.

2. The method of claim 1, wherein determining the particular application server from the at least two application servers to send the identified request for processing includes:

ranking the at least two application servers based on a correlation of the locally-cached versions of the at least one runtime objects to the at least one object associated with the identified request; and

in response to a determination that each of the at least two application servers includes a locally-cached version of the at least one runtime version of the at least one identified object;

identifying a second object in the model-based application associated with the identified request, the second object being different than any of the identified at least one object; and

ranking the at least two application servers based on a correlation of the locally-cached versions of the at least one runtime objects to the second object associated with the identified request.

3. The method of claim 2, wherein determining the particular application server from the at least two application servers to send the identified request for processing is based, at least in part, on a relatively higher ranking of the particular application server as compared to the other application servers of the at least two application servers.

4. The method of claim 1, wherein the cache map includes information on the local cache of each application server, where each local cache stores each runtime object available at the respective application server.

5. The method of claim 4, wherein the cache map is updated in response to changes to any local cache of any of the application servers associated with the multi-tenant system, wherein the cache map is updated by receiving updates on changes to the local caches associated with the plurality of application servers from listeners located at and executed by each application server, wherein each listener monitors and provides updated local cache information to the load balancer in response to changes to the local cache of the listener'"'"'s respective application server.

6. The method of claim 1, wherein identifying the at least one object in the model-based application associated with identified request includes:

identifying at least one object required to respond to the identified request; and

identifying at least one object associated with at least one potential operation to be performed subsequent to the initial response to the identified request.

7. The method of claim 6, wherein identifying the at least one object associated with at least one potential operation to be performed subsequent to the initial response to the identified request is based on a relationship of the at least one object associated with the at least one potential object to the at least one identified object required to respond to the identified request within the model-based application.

8. The method of claim 1, wherein the determination of the particular application server to send the identified request for processing is based on an algorithm weighing availability of locally-cached versions of the at least one runtime version at each of the application servers and the relative processing load of each application server.

9. The method of claim 1, wherein identifying the at least one object in the model-based application associated with the identified request is based, at least in part, on the identity of a user associated with request.

18. The method of claim 2, wherein the identified second object in the model-based application associated with the identified request is needed for additional processing of the model-based application.

10. A computer program product, the computer program product comprising computer-readable instructions embodied on non-transitory media, the instructions operable when executed by at least one computer to:

identify, at a load balancer, a request related to a model-based application executing in a multi-tenant system, the multi-tenant system associated with a plurality of application servers, and wherein the load balancer manages routing of identified requests related to the model-based application to particular application servers in the multi-tenant system;

identify, by the load balancer, at least one object in the model-based application associated with the identified request, wherein identifying the at least one object includes accessing a metadata repository associated with the model-based application to identify one or more objects associated with the identified request;

access, by the load balancer, a multi-tenant cache map storing information defining a current status of local caches of each of the plurality of application servers in the multi-tenant system maintained by the load balancer, wherein the multi-tenant cache map collects local cache information from each of the plurality of application servers in the multi-tenant system and identifies at least the locally-cached runtime versions of objects available in the corresponding local cache of the particular application servers;

identify, by the load balancer using the multi-tenant cache map, at least two application servers from the plurality of application servers based on a determination that the at least two application servers include, at a time the request is identified, a locally-cached version of at least one runtime version of the at least one identified object in the model-based application as determined based on the current status of the local caches of the at least two application servers as defined in the multi-tenant map; and

in response to identifying the at least two application servers, determine, by the load balancer, a particular application server from the at least two application servers to send the identified request for processing based at least in part on a combination of the locally-cached version of the at least one runtime version being available at the particular application server and the relative processing load of the particular application server as compared to the other application servers in the at least two identified application servers; and

send, by the load balancer, the identified request to the determined particular application server for processing.

11. The computer program product of claim 10, wherein determining the particular application server from the at least two application servers to send the identified request for processing includes:

ranking the at least two application servers based on a correlation of the locally-cached versions of the at least one runtime objects to the at least one object associated with the identified request.

12. The computer program product of claim 11, wherein determining the particular application server from the at least two application servers to send the identified request for processing is based, at least in part, on a relatively higher ranking of the particular application server as compared to the other application servers.

13. The computer program product of claim 10, wherein identifying the at least one object in the model-based application associated with identified request includes accessing a metadata repository associated with the model-based application to identify one or more design time objects associated with the identified request.

14. The computer program product of claim 10, wherein the cache map includes information on the local cache of each application server, where each local cache stores each runtime object available at the respective application server, wherein the cache map is updated in response to changes to any local cache of any of the application servers associated with the multi-tenant system, and wherein the cache map is updated by receiving updates on changes to the local caches associated with the plurality of application servers from listeners located at and executed by each application server, wherein each listener monitors and provides updated local cache information to the load balancer in response to changes to the local cache of the listener'"'"'s respective application server.

15. The computer program product of claim 10, wherein identifying the at least one object in the model-based application associated with identified request includes:

identifying at least one object required to respond to the identified request; and

identifying at least one object associated with at least one potential operation to be performed subsequent to the initial response to the identified request, wherein identifying the at least one object associated with at least one potential operation to be performed subsequent to the initial response to the identified request is based on a relationship of the at least one object associated with the at least one potential object to the at least one identified object required to respond to the identified request within the model-based application.

16. The computer program product of claim 10, wherein the determination of the particular application server to send the identified request for processing is based on an algorithm weighing availability of locally-cached versions of the at least one runtime version at each of the application servers and the relative processing load of each application server.

17. A system, comprising:

at least one processor;

a computer-readable storage medium coupled to the at least one processor having instructions stored thereon which, when executed by the at least one processor, cause the processor to perform operations comprising;

identifying, at a load balancer, a request related to a model-based application executing in a multi-tenant system, wherein the multi-tenant system is associated with a plurality of application servers, and wherein the load balancer manages routing of identified requests related to the model-based application to particular application servers in the multi-tenant system;

identifying, by the load balancer, at least one object in the model-based application associated with the identified request, wherein identifying the at least one object includes accessing a metadata repository associated with the model-based application to identify one or more objects associated with the identified request;

accessing, by the load balancer, a multi-tenant cache map storing information defining a current status of local caches of each of the plurality of application servers in the multi-tenant system maintained by the load balancer, wherein the multi-tenant cache map collects local cache information from each of the plurality of application servers in the multi-tenant system and identifies at least the locally-cached runtime versions of objects available in the corresponding local cache of the particular application servers;

identifying, by the load balancer using the multi-tenant cache map, at least two application servers from the plurality of application servers based on a determination that the at least two application servers include, at a time the request is identified, a locally-cached version of at least one runtime version of the at least one identified object in the model-based application as determined based on the current status of the local caches of the at least two application servers as defined in the multi-tenant map; and

in response to identifying the at least two application servers, determining, by the load balancer, a particular application server from the at least two application servers to send the identified request for processing based at least in part on a combination of the locally-cached version of the at least one runtime version being available at the particular application server and the relative processing load of the particular application server as compared to the other application servers in the at least two identified application servers; and

sending, by the load balancer, the identified request to the determined particular application server for processing.