Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Framework for multiple-target service routing

IP.com Disclosure Number: IPCOM000239099D
Publication Date: 2014-Oct-10
Document File: 3 page(s) / 59K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a framework to efficiently route a service request to multiple targets. The framework coordinates the multi-target services invocation by providing a default service result aggregator and allowing a service provider to plug in and take control of the services request.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

Framework for multiple-target service routing

A method is needed to route a service request to multiple targets. A service can be a Simple Object Access Protocol (SOAP) request, a Representational State Transfer (REST) request, or any other kind of client-server request. The existing approach is for the client to take on this burden, and individually call each service. Major drawbacks to this approach are that the client needs to understand how to aggregate all the results, the target service(s) does not have an opportunity to optimize the operation nor the response, and the client needs to directly contact each of the target endpoints.

The novel contribution is a framework that takes the responsibility for coordinating a multi-target services invocation by providing a default service result aggregator and allowing a service provider to plug in and take control of the services request. This supports optimized multi-target requests by individual service providers. The central controller also contacts each of the target servers,

which simplifies the scenario for the client because the client then only needs to talk to the central controller .

Figure: Example embodiment

Referring to the figure, the left side shows a set of clients that wants to invoke services on different targets, which are shown on the right. In this example, each target has two services available, A and B. "Services" can be any kind of invocable service such as REST endpoints, SOAP endpoints, Remote Method Invocation (RMI) calls, Remote Procedure Calls (RPCs), in-memory calls,database calls, etc. The controller is the central part of the framework, and can hold optional service plugins and default service helpers.

1


Page 02 of 3

The first novel aspect of this framework is the presence of a default aggregator . This inner service resides in the central controller and is responsible for calling services on the target on behalf of the clients and aggregating the results from the services invocations so the client only has to work with a single merged response.

One example, using REST calls, is if "Service B" corresponds to a REST endpoint "/serviceB/info". This service returns a JavaScript Object Notation (JSON) with the associated hostname; thus, { "host" : "target1" }, {"host" : "targetN"}, etc.

The client then passes a routing context to the controller, which has two pieces of information: a list of targets, and a serv...