Legacy application migration to real time, parallel performance cloud

• US 10,620,990 B2
• Filed: 01/30/2017
• Issued: 04/14/2020
• Est. Priority Date: 08/27/2010
• Status: Active Grant

• Current Assignee: UST Global (Singapore) Pte Ltd. (UST Global Incorporated)
• Original Assignee: UST Global (Singapore) Pte Ltd. (UST Global Incorporated)
• Inventors: Bachelor, Douglas Wiley, Curbelo, Raul Hugo, Elkins, Elizabeth Winters, McGrath, Christie Patrick, Moss, Simon Byford, Fountain, Thomas C.
• Primary Examiner(s): Onat, Umut
• Application Number:
  US15/419,937
• Publication Number:
  US 20170139741A1
• Time in Patent Office: 1,170 Days
• Field of Search: None
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06N 3/02 Neural networks
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A system for operating a legacy software application is presented. The system includes a distributed processing service. A wrapper software object is configured both to receive processing requests to a legacy software application from outside the distributed processing service and to send the processing requests using the distributed processing service. Additionally, an encapsulated software object includes the legacy software application and an exoskeleton connection service. The exoskeleton connection service is both configured to accept processing requests from the distributed processing service, and mapped to an application programming interface of the legacy software application.

Claims

1. A system for operating a legacy software application, comprising:

a distributed processing service having networked hardware servers;

a wrapper software object configured both to receive processing requests to the legacy software application from outside the distributed processing service and to send the processing requests using the distributed processing service;

an encapsulated software object running on at least one of the networked hardware servers that includes the legacy software application and an exoskeleton connection service that is both configured to accept processing requests from the distributed processing service and mapped to an application programming interface of the legacy software application, wherein there are at least two of the encapsulated software objects;

a load and queue manager configured to select an encapsulated software object from the at least two encapsulated software objects; and

a dispatcher software object configured to receive the request sent by the wrapper software object and send the request to the selected encapsulated software object.

2. The system for operating the legacy software application of claim 1, wherein the load and queue manager includes:

a load balance software object configured to monitor the at least two encapsulated software objects; and

a queue management software object configured to monitor a queue of units of work sent to one of the at least two encapsulated software objects.

3. The system for operating the legacy software application of claim 1, wherein the load and queue manager is configured to select the selected encapsulated software object in a round robin of the at least two encapsulated software objects.

4. The system for operating the legacy software application of claim 1, wherein the load and queue manager is configured to select the selected encapsulated software object based on a threshold.

5. The system for operating the legacy software application of claim 1, wherein the load and queue manager is configured to cause an additional encapsulated software object to be created if the load and queue manager determines that each of the at least two encapsulated software objects are unavailable.

6. The system for operating the legacy software application of claim 5, further comprising a database configured to store a partial result of a previous execution of the encapsulated software object, and wherein the load and queue manager is configured to use the partial result as a parameter of the additional encapsulated software object.

7. The system for operating the legacy software application of claim 1, wherein the dispatcher object is configured to increment an in-flight count each when it sends a request to the selected encapsulated software object, and further comprising a complete message object configured to decrement the in-flight count upon receiving an indication that the selected encapsulated software object has completed processing the request.

8. A method for operating a legacy software application, comprising:

mapping, by a wrapper object in a cloud computing environment that includes a distributed processing service having networked hardware servers, a processing request written in an application programming interface of the legacy software application to the protocols of the distributed processing service;

sending, by the wrapper object through the distributed processing service, the mapped processing request to a dispatcher object;

sending, by the dispatcher object through the distributed processing service, the mapped processing request both to a load balance object and to a queue management object;

deploying, by either the load balance object or the queue management object and based on a load evaluation, an instance of an encapsulated software object into the cloud computing environment, wherein the load balance object and the queue management object are operable to create new nodes from the networked hardware servers;

sending, by the dispatcher to the instance of the encapsulated software object, the mapped processing request;

passing, by the instance of the encapsulated software object, the mapped request to the application programming interface of the legacy software application; and

executing, by an instance of the legacy software application within the encapsulated software object on at least one of the networked hardware servers, the request.

9. The method for operating the legacy software application of claim 8, further comprising modifying, by an additional software object, the mapped processing request.

10. A system for operating a legacy software application, comprising:

a distributed processing service having networked hardware servers;

a wrapper software object configured both to receive processing requests to the legacy software application from outside the distributed processing service and to send the processing requests using the distributed processing service;

at least two encapsulated software objects that each include the legacy software application and an exoskeleton connection service that are both configured to accept processing requests from the distributed processing service and mapped to an application programming interface of the legacy software application, the at least two encapsulated software objects running on at least one of the networked hardware servers;

a load and queue manager configured to select an encapsulated software object from the at least two encapsulated software objects;

a master dispatcher object configured to receive the request sent by the wrapper software object and send the request to the selected one of the at least two encapsulated software objects; and

a slave dispatcher object configured to perform the functions of the master dispatcher object in the event communication between the master dispatcher object and the slave dispatcher object are disrupted.

11. The system for operating the legacy software application of claim 10, wherein the master dispatcher object and the slave dispatcher object are configured to operate on different servers of the cloud computing environment.