SERVICE ABSTRACTION LAYER FOR ACCESSING A PLURALITY OF SERVICES
Various embodiments of systems and methods for accessing a plurality of services using a service abstraction layer are described herein. A plurality of services from one or more service provider is registered in a service abstraction layer. A request, from a service requestor, for accessing at least one service of the registered plurality of services is received at the service abstraction layer. Further, the received service request, at a service invoker of the service abstraction layer is forwarded to at least one corresponding service provider. Furthermore, successful execution of the requested service by the corresponding service providers is determined at the service invoker. Based on the determination, a response from the corresponding service provider is returned to the service requestor. Therefore, communication between the service requestor and the multiple service providers is handled by the service abstraction layer, which acts as a centralized layer.
1 . An article of manufacture including a computer readable storage medium to tangibly store instructions, which when executed by a computer, cause the computer to:
receive, at a service abstraction layer, at least one request from a service requestor for accessing at least one service of a preregistered plurality of services;
forward, at a service invoker of the service abstraction layer, the received at least one request to at least one corresponding service provider;
determine, at the service invoker, whether the at least one requested service is successfully executed by the at least one corresponding service provider; and
based on the determination, return a response from the at least one corresponding service provider to the service requestor.
2 . The article of manufacture of claim 1 , wherein the plurality of services from one or more service providers are registered in a service registry of the service abstraction layer.
3 . The article of manufacture of claim 1 , wherein the received at least one request is stacked by a queue manager and the at least one request is forwarded to the service invoker using a first-in-first-out approach.
4 . The article of manufacture of claim 1 , wherein the at least one request is dynamically configured to comprise at least one of a type of service, a payload, a response callback handler type, a service requestor ID, a retry count, and a timeout period.
5 . The article of manufacture of claim 1 , wherein returning the response comprises at least one of updating a user interface (UI) of the service requestor with a response received from the at least one corresponding service provider and storing the response received from the at least one corresponding service provider at a predetermined registry, if the at least one request is successfully executed by the at least one corresponding source.
6 . The article of manufacture of claim 1 , wherein returning the response comprises queuing the at least one request for execution for a predetermined number of attempts, if the at least one requested service is not successfully executed by the at least one corresponding service provider.
7 . The article of manufacture of claim 6 , wherein returning the response further comprises updating the service requestor with an error message, if the at least one requested service is not successfully executed by the at least one corresponding service provider after the predetermined number of attempts.
8 . A computerized method for accessing a plurality of services from one or more sources using a service abstraction layer, the method comprising:
receiving, at the service abstraction layer, at least one request from a service requestor for accessing at least one service of the preregistered plurality of services;
forwarding, at the service invoker of the service abstraction layer, the received at least one request to at least one corresponding service provider;
determining, at the service invoker, whether the at least one requested service is successfully executed by the at least one corresponding service provider; and
based on the determination, returning a response from the at least one corresponding service provider to the service requestor.
9 . The computerized method of claim 8 , wherein the plurality of services from one or more service provider are registered in a service registry of the service abstraction layer.
10 . The computerized method of claim 8 , wherein the received at least one request is stacked by a queue manager and the at least one request is forwarded to the service invoker using a first-in-first-out approach.
11 . The computerized method of claim 8 , wherein the at least one request is dynamically configured to comprise at least one of a type of service, a payload, a response callback handler type, a service requestor ID, a retry count, and a timeout period.
12 . The computerized method of claim 8 , wherein returning the response comprises at least one of updating a user interface (UI) of the service requestor with a response received from the at least one corresponding service provider and storing the response received from the at least one corresponding service provider at a predetermined registry, if the at least one requested service is successfully executed by the at least one corresponding service provider.
13 . The computerized method of claim 8 , wherein returning the response comprises queuing the at least one request for execution for a predetermined number of attempts, if the at least one requested service is not successfully executed by the at least one corresponding service provider.
14 . The computerized method of claim 13 , wherein returning the response further comprises updating the service requestor with an error message, if the at least one requested service is not successfully executed by the at least one corresponding service provider after the predetermined number of attempts.
15 . A computer system for accessing a plurality of services from one or more sources using a service abstraction layer, the system comprising:
a processor;
a memory coupled to the processor to store program code; and
the service abstraction layer residing in the memory, wherein the service abstraction layer comprises:
a service registry for registering the plurality of services from the one or more service provider;
a request queue to receive a request from a service requestor for accessing at least one service, from the registered plurality of services; and
a service invoker to forward the received at least one request to at least one corresponding service provider of the one or more service provider, receiving a response from the at least one corresponding service provider, and forwarding the response to the service requestor.
16 . The computer system of claim 15 , further comprising a queue manager to stack the received at least one request and to forward the at least one request to the service invoker using a first-in-first-out approach.
17 . The computer system of claim 15 , wherein the at least one request is dynamically configured to comprise at least one of a type of service, a payload, a response callback handler type, a service requestor ID, a retry count, and a timeout period.
18 . The computer system of claim 15 , wherein returning the response comprises at least one of updating a user interface (UI) of the service requestor with a response received from the at least one corresponding service provider and storing the response received from the at least one corresponding service provider at a predetermined registry, if the at least one requested service is successfully executed by the at least one corresponding service provider.
19 . The computer system of claim 15 , wherein returning the response comprises queuing the at least one request for execution for a predetermined number of attempts, if the at least one requested service is not successfully executed by the at least one corresponding service provider.
20 . The computer system of claim 19 , wherein returning the response further comprises updating the service requestor with an error message, if the at least one requested service is not successfully executed by the at least one corresponding service provider after the predetermined number of attempts.