Analytics mediation for microservice architectures
First Claim
1. A computer program product, the computer program product being tangibly embodied on a non-transitory computer-readable storage medium and comprising instructions that, when executed, are configured to cause at least one computing device to:
- receive a first registration request from a first microservice for registration within a microservice data directory of first data access metadata;
register the first data access metadata within the microservice data directory, in response to the first registration request;
receive a second registration request from a second microservice for registration within the microservice data directory of the second data access metadata;
register the second data access metadata within the microservice data directory, in response to the second registration request;
receive a data analytics request that requires first data of the first microservice and second data of the second microservice;
access the microservice data directory to obtain the first data access metadata characterizing a structure and access methodology for the first data of the first microservice, and the second access metadata characterizing a structure and access methodology for the second data of the second microservice;
obtain the first data of the first microservice using the first access metadata, and the second data of the second microservice using the second access metadata; and
provide the first data of the first microservice and the second data of the second microservice to thereby respond to the data analytics request.
1 Assignment
0 Petitions
Accused Products
Abstract
An analytics mediator facilitates operations of an analytics engine and a corresponding analytics user interface (UI) in analyzing operations of a plurality of microservices. The analytics mediator enables the analytics engine to execute various types of conventional and new types of analyses with respect to the microservices, and to present the results of such analyses using the analytics UI, in a manner that is highly convenient and efficient for a user of the analytics engine, while also maintaining an independence, scalability, and other advantageous features of the microservices.
6 Citations
16 Claims
-
1. A computer program product, the computer program product being tangibly embodied on a non-transitory computer-readable storage medium and comprising instructions that, when executed, are configured to cause at least one computing device to:
-
receive a first registration request from a first microservice for registration within a microservice data directory of first data access metadata; register the first data access metadata within the microservice data directory, in response to the first registration request; receive a second registration request from a second microservice for registration within the microservice data directory of the second data access metadata; register the second data access metadata within the microservice data directory, in response to the second registration request; receive a data analytics request that requires first data of the first microservice and second data of the second microservice; access the microservice data directory to obtain the first data access metadata characterizing a structure and access methodology for the first data of the first microservice, and the second access metadata characterizing a structure and access methodology for the second data of the second microservice; obtain the first data of the first microservice using the first access metadata, and the second data of the second microservice using the second access metadata; and provide the first data of the first microservice and the second data of the second microservice to thereby respond to the data analytics request. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A method of executing instructions stored on a non-transitory computer-readable storage medium using at least one processor, the method comprising:
-
receiving a first registration request from a first microservice for registration within a microservice data directory of first data access metadata characterizing a structure and access methodology for first data of the first microservice; registering the first data access metadata within the microservice data directory; receiving a second registration request from a second microservice for registration within the microservice data directory of second data access metadata characterizing a structure and access methodology for second data of the second microservice; registering the second data access metadata within the microservice data directory; receiving a data analytics request that requires the first data of the first microservice and the second data of the second microservice; accessing the microservice data directory to obtain the first data access metadata and the second access metadata; and obtaining the required first data of the first microservice and the second data of the second microservice including interfacing with the first microservice using the first data access metadata to obtain the first data of the first microservice and interfacing with the second microservice using the second data access metadata to obtain the second data of the second microservice to thereby respond to the data analytics request. - View Dependent Claims (10, 11, 12, 13)
-
-
14. A microservice comprising:
-
a microservice data repository configured to store data of the microservice; a microservice application program interface (API) configured to interact with a second microservice API of a second microservice to thereby provide a combined functionality of the microservice and the second microservice; and a data access mediator configured to interface with an analytics mediator to register microservice metadata characterizing the data of the microservice with the analytics mediator, and further configured, based on a data request from the analytics mediator formulated in accordance with the microservice metadata, to provide requested data from the microservice data to thereby enable combined analysis of the requested data together with second data of the second microservice, wherein the data access mediator includes a metadata repository configured to store the microservice metadata characterizing a structure, access methodology, and content of the data of the microservice data repository, and a directory interface configured to register the microservice metadata with a microservice data directory storing the microservice metadata along with second microservice metadata characterizing a structure, access methodology, and content of the second data of the second microservice. - View Dependent Claims (15, 16)
-
Specification