PROXY WITH A FUNCTION AS A SERVICE (FAAS) SUPPORT

• US 20180375712A1
• Filed: 06/21/2017
• Published: 12/27/2018
• Est. Priority Date: 06/21/2017
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Krohling, Juraci Paixao, Rupp, Heiko Wolfgang
• Granted Patent: US 11,050,607 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

An example method for processing a client request includes determining a set of functions to invoke for processing an initial request sent by a client to an application. The set of functions includes a function stored at a server. The method also includes invoking, by a proxy, the function at the server. The server provides the function as a function as a service (FAAS) for invocation by one or more third parties. The method further includes sending, by the proxy, a processed request to the application. The processed request is based on a result of the function. The method also includes receiving, by the proxy, a response to the processed request from the application.

Claims

1. A method of processing a client request, comprising:

determining a set of functions to invoke for processing an initial request sent by a client to an application, the set of functions including a function stored at a server;

invoking, by a proxy, the function at the server, the server providing the function as a function as a service (FAAS) for invocation by one or more third parties;

sending, by the proxy, a processed request to the application, the processed request being based on a result of the function; and

receiving, by the proxy, a response to the processed request from the application.

2. The method of claim 1, wherein the set of functions includes a second function stored at a second server, the method further comprising:

invoking, by the proxy, the second function at the second server, the second server providing the second function as a FAAS for invocation by one or more third parties; and

generating the processed request, the processed request being based on a result of the second function.

3. The method of claim 1, further comprising:

receiving, by the proxy, the processed request.

4. The method of claim 1, further comprising:

determining whether to invoke one or more functions for processing the response.

5. The method of claim 4, further comprising:

in response to a determination to invoke a second function for processing the response, invoking the second function, the second function being stored at a second server providing the second function as a FAAS for invocation by one or more third parties; and

receiving, by the proxy, a processed response, the processed response being based on a result of the second function.

6. The method of claim 5, further comprising:

sending, by the proxy, the processed response to the client, the processed response being responsive to the initial request.

7. The method of claim 5, wherein the second set of functions includes a third function stored at a third server, the method further comprising:

invoking, by the proxy, the third function at the third server, the third server providing the third function as a FAAS for invocation by one or more third parties, wherein the processed request is based on a result of the third function.

8. The method of claim 1, wherein the response from the application is responsive to the initial request.

9. The method of claim 1, further comprising:

sending a query for functions to one or more function catalogues that store one or more functions;

receiving one or more functions responsive to the one or more queries; and

storing the one or more functions.

10. A system for processing a client request, comprising:

a proxy server that receives an initial request sent by a client to an application; and

a FAAS provider that determines a function to invoke for processing the initial request and invokes the function, wherein the function is stored at a server that provides the function as a FAAS for invocation by one or more third parties,

wherein the proxy sends a processed request to the application and receives a response to the processed request from the application, wherein the processed request is based on a result of the function.

11. The system of claim 10, wherein the FAAS provider determines a second function to invoke for processing the initial request and invokes the second function, wherein the second function is stored at a second server that provides the second function as a FAAS for invocation by one or more third parties, and the processed request is based on a result of the second function.

12. The system of claim 10, wherein the first server is different from the second server.

13. The system of claim 10, wherein the FAAS provider generates the processed request based on a result of the function, and the proxy receives the processed request from the FAAS provider.

14. The system of claim 10, wherein the proxy sends the response to the FAAS provider, and the FAAS provider determines whether to invoke one or more functions for processing the response.

15. The system of claim 14, wherein in response to a determination to invoke a second function for processing the response, the FAAS provider invokes the second function, and wherein the second function is stored at a second server providing the second function as a FAAS for invocation by one or more third parties.

16. The system of claim 15, wherein the FAAS provider generates a processed response based on a result of the second function.

17. The system of claim 16, wherein the proxy receives the processed response from the FAAS provider and sends the process response to the client, and wherein the processed response is responsive to the initial request.

18. The system of claim 15, wherein the first server is different from the second server.

19. The system of claim 15, wherein the first server is the same as the second server.

20. A machine-readable medium comprising a plurality of machine-readable instructions that when executed by one or more processors is adapted to cause the one or more processors to perform a method comprising:

determining a set of functions to invoke for processing an initial request sent by a client to an application, the set of functions including a function stored at a server;

invoking, by a proxy, the function at the server, the server providing the function as a FAAS for invocation by one or more third parties;

sending, by the proxy, a processed request to the application, the processed request being based on a result of the function; and

receiving, by the proxy, a response to the processed request from the application.