SERVICE REQUEST PROCESSING

• US 20140344340A1
• Filed: 05/16/2014
• Published: 11/20/2014
• Est. Priority Date: 05/16/2013
• Status: Active Grant

• Current Assignee: Vmware LLC (Broadcom, Inc.)
• Original Assignee: VMware, Inc. (Broadcom, Inc.)
• Inventors: TANG, Mingjun, ZHAI, Lei
• Granted Patent: US 9,672,053 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45575 Starting, stopping, suspending or resuming virtual machine instances
• CPC Class Codes: G06F 9/44536 Selecting among different versions
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/50 Allocation of resources, e.g. of the central processing unit [CPU]
• CPC Class Codes: G06F 9/5005 to service a request
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/5061 Partitioning or combining of resources
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: G06F 9/5083 Techniques for rebalancing the load in a distributed system
• CPC Class Codes: G06F 9/5088 involving task migration
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 67/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals

Abstract

An example method to perform service request processing may comprise receiving, from a client device, a request associated with a first version of a service, the service being accessible via the server. The method may further comprise, in response to determination that version conversion from the first version to a second version of the service is required, converting the request to be compatible with the second version of the service and processing the converted request to generate a response associated with the second version. In this case, the method may further comprise converting the response to be compatible with the first version of the service; and sending, to the client device, the converted response that is compatible with the first version.

Claims

1. A method for a server to perform service request processing, the method comprising:

receiving, from a client device, a request associated with a first version of a service, the service being accessible via the server;

in response to determination that version conversion from the first version to a second version of the service is required,

converting the request to be compatible with the second version of the service;

processing the converted request to generate a response associated with the second version;

converting the response to be compatible with the first version of the service; and

sending, to the client device, the converted response that is compatible with the first version.

2. The method of claim 1, wherein converting the request to be compatible with the second version of the service comprises using a chain of adapters supported by the server to successively convert from the first version to an intermediate version and from the intermediate version to the second version.

3. The method of claim 2, wherein converting the request to be compatible with the second version of the service further comprises using a dispatcher supported by the server to select, from the chain of adapters, an adapter associated with the first version to start the conversion.

4. The method of claim 2, wherein converting the request to be compatible with the second version of the service further comprises using a terminal adapter supported by the server to modify the converted request into a format readable by a backend system implementing the service.

5. The method of claim 1, wherein converting the response to be compatible with the first version of the service comprises using a chain of adapters to successively convert the response from the second version to an intermediate version and from the intermediate version to the first version.

6. The method of claim 1, wherein converting the request to be compatible with the second version of the service, or the response to be compatible with the first version of the service, comprises modifying a header or a body, or both, of the request or response.

7. The method of claim 1, wherein determination that version conversion comprises retrieving the first version from a header of the request and comparing the first version with the second version.

8. The method of claim 1, wherein processing the converted request comprises invoking an implementation of the service supported by a backend system.

9. The method of claim 1, wherein the request is a representational state transfer (REST) application programming interface (API) call to the server to retrieve, modify, create or remove a representation of an object stored in a database.

10. The method of claim 9, wherein the request or converted response, or both, includes the representation of the object in one of the following format:

extensible markup language (XML) and Javascript object notation (JSON).

11. A non-transitory computer-readable storage medium that includes a set of instructions which, in response to execution by a processor, causes the processor to perform service request processing, comprising:

receiving, from a client device, a request associated with a first version of a service, the service being accessible via the server;

in response to determination that version conversion from the first version to a second version of the service is required,

converting the request to be compatible with the second version of the service;

processing the converted request to generate a response associated with the second version;

converting the response to be compatible with the first version of the service; and

sending, to the client device, the converted response that is compatible with the first version.

12. The non-transitory computer-readable storage medium of claim 11, wherein converting the request to be compatible with the second version of the service comprises using a chain of adapters supported by the server to successively convert from the first version to an intermediate version and from the intermediate version to the second version.

13. The non-transitory computer-readable storage medium of claim 12, wherein converting the request to be compatible with the second version of the service further comprises using a dispatcher supported by the server to select, from the chain, an adapter associated with the first version to start the conversion.

14. The non-transitory computer-readable storage medium of claim 12, wherein converting the request to be compatible with the second version of the service further comprises using a terminal adapter supported by the server to modify the converted request into a format readable by a backend system implementing the service.

15. The non-transitory computer-readable storage medium of claim 11, converting the response to be compatible with the first version of the service comprises using a chain of adapters to successively convert the response from the second version to an intermediate version and from the intermediate version to the first version.

16. The non-transitory computer-readable storage medium of claim 11, converting the request to be compatible with the second version of the service, or the response to be compatible with the first version of the service, comprises modifying a header or a body, or both, of the request or response.

17. The non-transitory computer-readable storage medium of claim 11, wherein the request is a representational state transfer (REST) application programming interface (API) call to the server to retrieve, modify, create or remove a representation of an object stored in a database.

18. A computer system for service request processing, wherein the computer system comprises:

a processor; and

a non-transitory computer-readable storage medium having stored thereon instructions that, when executed by the processor, cause the processor to;

receive, from a client device, a request associated with a first version of a service, the service being accessible via the server;

in response to determination that version conversion from the first version to a second version of the service is required,

convert the request to be compatible with the second version of the service;

process the converted request to generate a response associated with the second version;

convert the response to be compatible with the first version of the service; and

send, to the client device, the converted response that is compatible with the first version.

19. The computer system of claim 18, wherein the instructions for converting the request to be compatible with the second version of the service further cause the processor to implement one or more of the following:

a chain of adapters to successively convert from the first version to an intermediate version and from the intermediate version to the second version;

a dispatcher to select, from the chain, an adapter associated with the first version to start the conversion; and

a terminal adapter supported by the server to modify the converted request into a format readable by a backend system implementing the service.

20. The computer system of claim 18, wherein the instructions for converting the response to be compatible with the first version of the service, when executed by the processor, further cause the processor to implement:

a chain of adapters to successively convert the response from the second version to an intermediate version and from the intermediate version to the first version.

21. The computer system of claim 18, wherein the instructions for determining that version conversion is required further cause the processor to:

retrieve the first version from a header of the request and comparing the first version with the second version.

22. The computer system of claim 18, wherein the instructions for processing the converted request further cause the processor to invoke an implementation of the service supported by a backend system.