Processing an operation with a plurality of processing steps

• US 10,362,097 B1
• Filed: 06/05/2018
• Issued: 07/23/2019
• Est. Priority Date: 06/05/2018
• Status: Active Grant

• Current Assignee: Capital One Services LLC (Capital One Financial Corporation)
• Original Assignee: Capital One Services LLC (Capital One Financial Corporation)
• Inventors: Gupta, Tuhin, Koduri, Prabhu Ranjith Kumar, Vaidyanathan, Parameswaran V, John, Joji Thomas, Jacob, Ashwin, Thomas, Siju, Gleaton, Kevin, Singh, Amit, Chandrasekharan, Vivek Paul, Jose, Mithun, Aluru, Venkata Sudha, Pemmasani, Manoj, Reid, Justin, Newell, Michael P.
• Primary Examiner(s): Biagini, Christopher
• Application Number:
  US16/000,190
• Time in Patent Office: 413 Days
• CPC Class Codes: G06F 16/188 Virtual file systems
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

A device may receive a request for an operation that includes a plurality of processing steps may identify metadata information. The device may determine a first processing step, and select a first microservice to call and a first transport protocol to utilize to call the first microservice. The device may call the first microservice, and may receive, from the first microservice a first output. The device may determine a second processing step, and select a second microservice to call and a second transport protocol to utilize to call the second microservice, wherein the second transport protocol is different from the first transport protocol. The device may call the second microservice, and may receive, from the second microservice, a second output. The device may provide a response to the request based on the first output and the second output.

Claims

1. A device, comprising:

one or more memory devices; and

one or more processors, operatively coupled to the one or more memory devices, to;

receive a request for an operation that includes a plurality of processing steps;

process the request to identify metadata information;

determine a first processing step, of the plurality of processing steps, based on the metadata information;

process the metadata information to select a first microservice, of a plurality of microservices, to call and a first transport protocol, of a plurality of transport protocols, to utilize to call the first microservice;

call a first plugin to cause the first plugin to validate a first portion of the metadata information identifying the first processing step and the first microservice;

call, utilizing the first transport protocol and based on the first plugin validating the first portion of the metadata information, the first microservice to cause the first microservice to perform the first processing step;

receive, from the first microservice and based on calling the first microservice, a first output that indicates a result of the first microservice performing the first processing step;

call a second plugin to cause the second plugin to evaluate the first output;

determine, based on the first output and the metadata information, a second processing step of the plurality of processing steps;

process the first output and the metadata information to select a second microservice, of the plurality of microservices, to call and a second transport protocol, of the plurality of transport protocols, to utilize to call the second microservice,

wherein the second transport protocol is different from the first transport protocol;

call a third plugin to cause the third plugin to validate a second portion of the metadata information identifying the second processing step and the second microservice;

call, utilizing the second transport protocol and based on the third plugin validating the second portion of the metadata information, the second microservice to cause the second microservice to perform the second processing step;

receive, from the second microservice and based on calling the second microservice, a second output that indicates a result of the second microservice performing the second processing step; and

provide a response to the request based on the first output and the second output.

2. The device of claim 1, wherein the first microservice is different from the second microservice.

3. The device of claim 1, wherein the one or more processors are further to:

receive, from the first plugin and based on calling the first plugin, a first signal that indicates validity of the first portion of the metadata information;

send the first signal to one or more servers for storage;

receive, from the second plugin and based on calling the second plugin, a first outcome related to the first processing step;

send the first outcome to the one or more servers for storage;

receive, from the third plugin and based on calling the third plugin, a second signal that indicates validity of the second portion of the metadata information;

send the second signal to the one or more servers for storage;

call a fourth plugin to cause the fourth plugin to evaluate the second output;

receive, from the fourth plugin and based on calling the fourth plugin, a second outcome related to the second processing step; and

send the second outcome to the one or more servers for storage.

4. The device of claim 1, wherein the one or more processors are further to:

receive, from the first plugin and based on calling the first plugin, an outcome that indicates that an exception has occurred related to the first processing step.

5. The device of claim 4, wherein the one or more processors are further to:

determine, based on the outcome, a retry rate related to the first processing step;

determine, based on the outcome, a retry period related to the first processing step; and

create a schedule, based on the retry rate and the retry period, to call, utilizing the first transport protocol, the first microservice to cause the first microservice to perform the first processing step.

6. The device of claim 1, wherein the first transport protocol is synchronous and the second transport protocol is asynchronous, or

the first transport protocol is asynchronous and the second transport protocol is synchronous.

7. The device of claim 1, wherein the request is a first request sent by a first client device using a first protocol;

and

where the one or more processors are further to;

receive a second request sent by a second client device using a second protocol; and

distinguish between the first request and the second request based on the first protocol and the second protocol.

8. The device of claim 1, wherein the one or more processors, when processing the request, are to:

parse the request to determine a name of the operation;

send a query, using the name, to a metadata server; and

receive, from the metadata server based on the query, the metadata information.

9. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors, cause the one or more processors to;

receive a request for an operation that includes a plurality of processing steps;

process the request to identify metadata information;

determine a first processing step, of the plurality of processing steps, based on the metadata information;

process the metadata information to select a first microservice, of a plurality of microservices, to call and a first transport protocol, of a plurality of transport protocols, to utilize to call the first microservice;

call a first plugin to cause the first plugin to validate a first portion of the metadata information identifying the first processing step and the first microservice;

send first information related to the first processing step, the first microservice, and the first transport protocol to one or more servers for storage;

call, utilizing the first transport protocol and based on the first plugin validating the first portion of the metadata information, the first microservice to cause the first microservice to perform the first processing step;

receive, from the first microservice and based on calling the first microservice, a first output that indicates a result of the first microservice performing the first processing step;

call a second plugin to cause the second plugin to evaluate the first output;

determine, based on the first output and the metadata information, a second processing step of the plurality of processing steps;

process the first output and the metadata information to select a second microservice, of the plurality of microservices, to call and a second transport protocol, of the plurality of transport protocols, to utilize to call the second microservice,

wherein the second transport protocol utilizes a different transmission synchronization from the first transport protocol;

call a third plugin to cause the third plugin to validate a second portion of the metadata information identifying the second processing step and the second microservice;

send second information related to the second processing step, the second microservice, and the second transport protocol to the one or more servers for storage;

call, utilizing the second transport protocol and based on the third plugin validating the second portion of the metadata information, the second microservice to cause the second microservice to perform the second processing step;

receive, from the second microservice, and based on calling the second microservice, a second output that indicates a result of the second microservice performing the second processing step; and

provide a response to the request based on the first output and the second output.

10. The non-transitory computer-readable medium of claim 9, wherein the first microservice is different from the second microservice.

11. The non-transitory computer-readable medium of claim 9, wherein the metadata information includes:

data that identifies a retry rate related to retrying the first processing step, and

data that identifies a retry period related to retrying the first processing step.

12. The non-transitory computer-readable medium of claim 9, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

receive, from the second plugin and based on calling the second plugin, a determination that indicates that an error has occurred related to the first processing step.

13. The non-transitory computer-readable medium of claim 12, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

determine, based on the determination that indicates that an error has occurred and the metadata information, a retry time related to the first processing step;

determine, based on the determination that indicates that an error has occurred and the metadata information, a retry quantity related to the first processing step; and

create a schedule, based on the retry time and the retry quantity, for calling, utilizing the first transport protocol, the first microservice to cause the first microservice to perform the first processing step.

14. The non-transitory computer-readable medium of claim 9, wherein the one or more instructions, that cause the one or more processors to process the request, cause the one or more processors to:

parse the request, using natural language processing, to determine a name of the operation;

send a query, using the name, to a metadata server; and

receive, from the metadata server based on the query, the metadata information.

15. A method, comprising:

receiving, by a server device, a request for an operation that includes a plurality of processing steps;

processing, by the server device, the request to identify metadata information;

determining, by the server device, a first processing step, of the plurality of processing steps, based on the metadata information;

processing, by the server device, the metadata information to select a first microservice, of a plurality of microservices, to call and a first transport protocol, of a plurality of transport protocols, to utilize to call the first microservice;

calling, by the server device, a first plugin to cause the first plugin to validate a first portion of the metadata information identifying the first processing step and the first microservice;

calling, by the server device, utilizing the first transport protocol, and based on the first plugin validating the first portion of the metadata information, the first microservice to cause the first microservice to perform the first processing step;

receiving, by the server device, from the first microservice, and based on calling the first microservice, a first output that indicates a result of the first microservice performing the first processing step;

calling, by the server device, a second plugin to cause the second plugin to evaluate the first output;

determining, by the server device and based on the first output and the metadata information, a second processing step of the plurality of processing steps;

processing, by the server device, the first output and the metadata information to select a second microservice, of the plurality of microservices, to call and a second transport protocol, of the plurality of transport protocols, to utilize to call the second microservice,

wherein the second transport protocol is different from the first transport protocol;

calling, by the server device, a third plugin to cause the third plugin to validate a second portion of the metadata information identifying the second processing step and the second microservice;

calling, by the server device, and utilizing the second transport protocol and based on the third plugin validating the second portion of the metadata information, the second microservice to cause the second microservice to perform the second processing step;

receiving, by the server device, from the second microservice, and based on calling the second microservice, a second output that indicates a result of the second microservice performing the second processing step;

sending, by the server device, information related to the first output and the second output to one or more servers for storage; and

providing, by the server device, a response to the request based on the first output and the second output.

16. The method of claim 15, wherein the first transport protocol has a different transmission synchronization from the second transport protocol.

17. The method of claim 15, wherein the first microservice is different from the second microservice.

18. The method of claim 15, further comprising:

generating an identification key identifying the first processing step; and

sending the identification key to the one or more servers for storage in association with the information related to the first output and the second output.

19. The method of claim 15, further comprising:

determining, based on the first output, that an exception has occurred related to the first processing step.

20. The method of claim 19, further comprising:

determining a retry time for reattempting the first processing step; and

calling, utilizing the first transport protocol and at the retry time, the first microservice to cause the first microservice to perform the first processing step.