METHOD AND SYSTEM FOR REDUCING SERVICE OVERHEAD IN SERVICE ORIENTED ARCHITECTURES

• US 20120226737A1
• Filed: 03/28/2011
• Published: 09/06/2012
• Est. Priority Date: 03/01/2011
• Status: Active Grant

• Current Assignee: Infosys Limited
• Original Assignee: Infosys Technologies Limited (Infosys Limited)
• Inventors: Rajaraman, Prasanna, Ramasundaram, Sethuraman
• Granted Patent: US 8,874,640 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 9/44526 Plug-ins; Add-ons
• CPC Class Codes: G06F 9/5044 considering hardware capabilities

Abstract

A system and method for processing service request in service oriented architectures to minimize service overhead is provided. The method includes invoking a software service by a client by sending service request to a server hosting the software service. The method further includes receiving the software service request by the server and determining whether one or more portions of service logic software code should be executed by the client, based on information related to client capabilities. Thereafter, service logic software code is streamed to the client partly or in-total. The client executes service logic software code provided by the server. The server is pre-configured to execute or transfer one or more portions of service logic software code to the client based on client capability information and extent of affinity of the service for server-specific resources. The server executes the software service partly or in-total based on the configuration.

Claims

1. A method for processing a service request in a service oriented architecture comprising one or more clients and one or more servers, the method comprising:

invoking a software service by a client, wherein the software service is invoked by sending a service request to a server hosting the software service;

receiving the software service request by the server and determining whether the software service should be executed by the client, wherein the determination is made by ascertaining whether the software service is enabled for client-side execution and is capable of being executed by the client;

providing service logic software code to the client for processing the service request, if it is determined that the software service is enabled for client-side execution and is capable of being executed by the client, wherein the service logic software code is provided to the client by streaming the code to the client;

executing the software service by the client upon receipt of service logic software code from the server; and

executing the requested software service by the server, if it is determined that the software service is not enabled for client-side execution or is not capable of being executed by the client.

2. The method of claim 1 further comprising following the receipt of service logic software code, executing subsequent requests for the software service by the client.

3. The method of claim 2 further comprising receiving updates of the service logic software code at regular intervals by the client.

4. The method of claim 1, wherein the service logic software code is streamed to the client by a service container application at the server hosting the code.

5. The method of claim 4, wherein the service logic software code is deployed within the service container application in a programming language mutually supported by the client and the server.

6. The method of claim 4, wherein the service logic software code is deployed within the service container application in a programming language that can be executed in a plurality of software platforms.

7. The method of claim 6, wherein the programming language is an ECMAScript.

8. The method of claim 6, wherein the programming language is a standardized programming language supported across multiple software platforms.

9. The method of claim 1, wherein the software service is enabled for being executed by the client partly or in-total based on the extent of affinity the service has for server-specific resources, further wherein the enablement is implemented by at least one of configuration by a system administrator at the server and automatic configuration at the server.

10. The method of claim 1, wherein the software service is enabled for being executed by the client partly or in-total based on information about client capabilities, further wherein the enablement is automatically configured by the server.

11. The method of claim 9, wherein the service logic software code includes one or more portions of the entire software code required for executing the service, wherein the one or more portions are developed and deployed within the service container application based on information about client capabilities.

12. The method of claim 9, wherein the software service is executed by the server partly or in-total based on the configuration at the server.

13. The method of claim 10, wherein determining whether the software service is capable of being executed by the client comprises:

determining whether the client has the necessary resources and libraries for executing the service logic software code; and

determining whether runtime execution of service logic software code is supported by the client.

14. The method of claim 10, wherein the determination regarding client capability for service execution is made by the server upon receiving client-capability information from the client as part of software handshake process.

15. The method of claim 10, wherein determining whether the software service is capable of being executed by the client further comprises determining whether requirements conforming to service security and validation are met by the client.

16. The method of claim 10, wherein determining whether the software service is capable of being executed by the client comprises estimating total system load including that of the client.

17. The method of claim 1, wherein the service logic software code is executed by the client using a software plug-in.

18. The method of claim 1, wherein the service logic software code is executed by the client using a sandbox.

19. The method of claim 1, wherein the service logic software code is executed by an intermediate infrastructure such as a proxy server.

20. The method of claim 1 wherein the software service request is a web service request.

21. A system for processing a service request in a service oriented architecture, the system comprising:

a client system comprising;

an XML marshaller configured to receive a service request and further configured to convert request objects into XML-formatted data;

a Service Logic Binding component configured to encapsulate XML-formatted data within a SOAP message and further configured to define rules for binding the SOAP message to a service request message;

a Service Logic Invoker configured to send the service request message to at least one of a server and a client container application based on determining whether the service can be executed at the client system;

a client container application configured to download service logic software code streamed from the server and further configured to execute the code in order to process the service request;

a Service Logic Response processor configured to process service response and deliver corresponding SOAP message to SOAP response interpreter;

a SOAP response interpreter configured to extract XML-formatted data from the SOAP message; and

an XML unmarshaller configured to extract service response object from XML-formatted data;

and

a server configured to stream service logic software code to the client system, the server comprising;

a service platform configured to host service logic software code corresponding to complete execution of service request, wherein the service logic software code is deployed at the service platform by a developer;

and

a service container application configured to host one or more portions of service logic software code that are client-compatible, wherein the client-compatible code corresponds to partial execution of the service request, further wherein the service container application is further configured to determine portions of service logic software code that are client-compatible.

22. The client system of claim 21, wherein the Service Logic Binding component is further configured to add custom headers to the service request message so that service logic software code is exchanged between the client container application and the server in a manner transparent to the client system.

23. The client system of claim 21, wherein the determination whether the service can be executed at the client system is made by the Service Logic Invoker based on establishing whether the service is enabled for client-side execution.

24. The client system of claim 21, wherein the determination that service is capable for client-side execution is made by the Service Logic Invoker based on establishing whether the service logic software code is downloadable from the server.

25. The server of claim 21, wherein a developer demarcates the one or more portions of service logic software code that are client-compatible and deploys the one or more portions at the service container application.

26. The server of claim 21, wherein the service container application comprises an interface for streaming the one or more portions of service logic software code to the client system.

27. The server of claim 21, wherein service logic software code corresponding to complete service implementation is deployed at the service container application, if it is determined that code corresponding to complete service implementation is client-compatible.

28. A computer program product comprising a computer usable medium having a computer readable program code embodied therein for processing a service request in a service oriented architecture comprising one or more clients and one or more servers, the computer program product comprising:

program instruction code for invoking a software service by a client, wherein the software service is invoked by sending a service request to a server hosting the software service;

program instruction code for receiving the software service request by the server and determining whether the software service should be executed by the client, wherein the determination is made by ascertaining whether the software service is enabled for client-side execution and is capable of being executed by the client;

program instruction code for providing service logic software code to the client for processing the service request, if it is determined that the software service is enabled for client-side execution and is capable of being executed by the client, wherein the service logic software code is provided to the client by streaming the code to the client;

program instruction code for executing the software service by the client upon receipt of service logic software code from the server; and

program instruction code for executing the requested software service by the server, if it is determined that the software service is not enabled for client-side execution or is not capable of being executed by the client.

29. The computer program product of claim 28 further comprising following the receipt of service logic software code, program instruction code for executing subsequent requests for the software service by the client.

30. The computer program product of claim 29 further comprising program instruction code for receiving updates of the service logic software code at regular intervals by the client.

31. The computer program product of claim 28, wherein program instruction code for determining whether the software service is capable of being executed by the client comprises:

program instruction code for determining whether the client has the necessary resources and libraries for executing the service logic software code; and

program instruction code for determining whether runtime execution of service logic software code is supported by the client.

32. The computer program product of claim 28, wherein program instruction code for determining whether the software service is capable of being executed by the client comprises program instruction code for determining whether requirements conforming to service security and validation are met by the client.

33. The computer program product of claim 28, wherein program instruction code for determining whether the software service is capable of being executed by the client comprises program instruction code for estimating total system load including that of the client.