Method and system for implementing application lineage metadata and registration
The invention relates to a system that implements application lineage metadata and registration. An embodiment of the present invention is directed to auto generating Application Lineage data. This may be accomplished by implementing code markers, such as @Annotations, within the code. An embodiment of the present invention may scan the code each time a build is kicked off by a continuous integration and continuous delivery (CI/CD) pipeline. At the end of the build, the documentation may be automatically generated with application lineage information.
1. A system for implementing application lineage metadata and registration, the system comprising:
a memory component that stores and manages code;
an interactive interface that communicates with a user via a communication network; and
a computer processor coupled to the memory component and the interactive interface and further configured to perform the steps of:
initiating a build process for code, wherein the build process comprises one or more plugins integrated with a build tool;
scanning, via one or the one or more plugins, the code for one or more predefined annotation markers that were added into the code;
identifying a corresponding content for each annotation marker;
automatically generating registry information in the form of a plurality of logical and physical catalogs that identify application lineage data associated with one or more assets or services of an ecosystem;
maintaining and storing the registry information in the memory component;
generating analytics based on the registry information; and
providing, via the interactive interface, a search function, filtering, and visualization data that graphically depicts the application lineage data comprising ownership traceability information.
2. The system of claim 1 , wherein the build process is initiated by a continuous integration and continuous delivery pipeline.
3. The system of claim 1 , wherein the one or more annotation markers comprise a predetermined symbol and one or more of: Publish API, Subscribe API, Publish Event, Subscribe Event, Persistent Database, Application Identifier and Component Identifier.
4. The system of claim 3 , wherein the predetermined symbol is not alphanumeric.
5. The system of claim 1 , wherein the registry information comprises a catalog with asset inventory and metadata that represents ownership and traceability.
6. The system of claim 5 , wherein the catalog comprises one or more of: API catalog, microservices catalog, applications catalog, events catalog, data catalog, metadata catalog, infrastructure catalog and configurations catalog.
7. The system of claim 1 , wherein the annotation markers represent a specific implementation pattern that is discovered by an automated discoverability feature.
8. The system of claim 1 , wherein the annotation markers are identified by scanning the code to identify a template that represents a specific industry standard.
9. The system of claim 1 , wherein the one or more assets or services of an ecosystem comprise Application assets, Events assets, API assets and Data Assets.
10. The system of claim 1 , wherein the visualization data is automatically generated and version each time the code is built.
11. A method for implementing application lineage metadata and registration, the method comprising the steps of:
initiating, via a computer processor, a build process for code, wherein the build process comprises one or more plugins integrated with a build tool;
scanning, via one of the one or more plugins, the code for one or more predefined annotation markers that were added into the code;
identifying, via the computer processor, a corresponding content for each annotation marker;
automatically, via the computer processor, generating registry information in the form of a plurality of logical and physical catalogs that identify application lineage data associated with one or more assets or services of an ecosystem;
maintaining and storing, via the computer processor, the registry information in memory component;
generating, via the computer processor, analytics based on the registry information; and
providing, via an interactive interface, a search function, filtering, and visualization data that graphically depicts the application lineage data comprising ownership traceability information.
12. The method of claim 11 , wherein the build process is initiated by a continuous integration and continuous delivery pipeline.
13. The method of claim 11 , wherein the one or more annotation markers comprise a predetermined symbol and one or more of: Publish API, Subscribe API, Publish Event, Subscribe Event, Persistent Database, Application Identifier and Component Identifier.
14. The method of claim 13 , wherein the predetermined symbol is not alphanumeric.
15. The method of claim 11 , wherein the registry information comprises a catalog with asset inventory and metadata that represents ownership and traceability.
16. The method of claim 15 , wherein the catalog comprises one or more of: API catalog, microservices catalog, applications catalog, events catalog, data catalog, metadata catalog, infrastructure catalog and configurations catalog.
17. The method of claim 11 , wherein the annotation markers represent a specific implementation pattern that is discovered by an automated discoverability feature.
18. The method of claim 11 , wherein the annotation markers are identified by scanning the code to identify a template that represents a specific industry standard.
19. The method of claim 11 , wherein the one or more assets or services of an ecosystem comprise Application assets, Events assets, API assets and Data Assets.
20. The method of claim 11 , wherein the visualization data is automatically generated and version each time the code is built.