Optimized service integration
An optimized service mediation framework may use customized tokens for reducing cost and latencies per transaction. In particular, a token service and an integration service may function together to generate customized tokens for use by network components within a transaction pathway. Each network component may access information with the token for a predetermined time period and/or for a predetermined number of service calls for service processing tasks related to mapping, security, governing, bridging, transforming, orchestrating, generating events, managing workloads, routing, validating, managing cache, encrypting, queuing and staging, commodity services, transaction management, and quality of service (QoS)/resiliency, among other things.
1. A non-transitory computer-readable storage medium having computer-executable program instructions stored thereon that when executed by a processor, cause the processor to perform:
(a) receiving, by a service router from a client device associated with a service requestor, a service request associated with a service implemented by at least one of a plurality of service providers;
(b) analyzing, by the service router, information within the service request to determine at least one policy for handling the service request based on information stored in an enhanced service repository;
(c) determining, by the service router, whether there exists, in a cache of the service router, a valid token associated with the service and the at least one policy;
(d) responsive to a determination that no valid token exists, transmitting, by the service router, the service request to an integration service;
(e) receiving, by the integration service, a generic token having a plurality of fields from a token service;
(f) generating, by the integration service, from the generic token, a customized token by populating each field of the generic token based, at least in part, on information within the service request and the at least one policy;
(g) receiving, by the service router from the integration service, the customized token for handling the service request;
(h) caching the customized token by the service router; and
(i) routing, by the service router, the customized token to one of the plurality of service providers.
2. The non-transitory computer-readable storage medium of claim 1 , wherein the service request includes an Extensible Markup Language (XML) table with rules for distinguishing between a plurality of services.
3. The non-transitory computer-readable storage medium of claim 1 , wherein the service request is chosen from the group consisting of: opening a bank account, registering for a credit card, and applying for a loan.
4. The non-transitory computer-readable storage medium of claim 1 , wherein the customized token includes a requestor application ID field, a provider segment field, an abstract service name field, and a concrete service name field.
5. The non-transitory computer-readable storage medium of claim 1 , wherein the customized token includes a time to live field, a refresh time field, a usage limit field, and a timeout field.
6. The non-transitory computer-readable storage medium of claim 1 , wherein the customized token comprises a service token.
7. The non-transitory computer-readable storage medium of claim 1 , wherein the analyzing comprises determining an address of the service provider associated with the service request.
8. The non-transitory computer-readable storage medium of claim 1 , wherein the customized token is valid for a predetermined number of service requests.
9. The non-transitory computer-readable storage medium of claim 8 , wherein the processor further performs: after the predetermined number of service requests, receiving a new customized token from the integration service.
10. The non-transitory computer-readable storage medium of claim 1 , wherein the customized token is valid for a predetermined length of time.