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 from an application, wherein the build process comprises one or more plugins integrated with a build tool, and wherein the code includes one or more predefined annotation markers;
scanning, via the one or more plugins, the code for the one or more predefined annotation markers that were added into the code, and scanning the code to identify at least one implementation pattern for the application, the at least one implementation pattern providing context for the code;
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, wherein the application lineage data is generated during the build process and based on the one or more predefined annotation markers;
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, a filtering function, 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 registry information comprises asset inventory and metadata that represents ownership and traceability.
4. The system of claim 1 , wherein the plurality of logical and physical catalogs comprise one or more of: API catalog, microservices catalog, applications catalog, events catalog, data catalog, metadata catalog, infrastructure catalog and configurations catalog.
5. 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.
6. The system of claim 1 , wherein the visualization data is automatically generated and versioned each time the code is built.
7. 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 from an application, wherein the build process comprises one or more plugins integrated with a build tool, and wherein the code includes one or more predefined annotation markers;
scanning, via the one or more plugins executed by the computer processor, the code for the one or more predefined annotation markers that were added into the code, and scanning the code to identify at least one implementation pattern for the application, the at least one implementation pattern providing context for the code;
automatically generating, via the computer processor, 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, wherein the application lineage data is generated during the build process and based on the one or more predefined annotation markers;
maintaining and storing, via the computer processor, the registry information in the memory component;
generating, via the computer processor, analytics based on the registry information; and
providing, via an interactive interface, a search function, a filtering function, and visualization data that graphically depicts the application lineage data comprising ownership traceability information.
8. The method of claim 7 , wherein the build process is initiated by a continuous integration and continuous delivery pipeline.
9. The method of claim 7 , wherein the registry information comprises asset inventory and metadata that represents ownership and traceability.
10. The method of claim 7 , wherein the plurality of logical and physical catalogs comprise one or more of: API catalog, microservices catalog, applications catalog, events catalog, data catalog, metadata catalog, infrastructure catalog and configurations catalog.
11. The method of claim 7 , wherein the one or more assets or services of an ecosystem comprise Application assets, Events assets, API assets and Data Assets.
12. The method of claim 7 , wherein the visualization data is automatically generated and versioned each time the code is built.
13. A non-transient computer readable medium containing program instructions for causing a computer to perform 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 from an application, wherein the build process comprises one or more plugins integrated with a build tool, and wherein the code includes one or more predefined annotation markers;
scanning, via the one or more plugins executed by the computer processor, the code for the one or more predefined annotation markers that were added into the code, and scanning the code to identify at least one implementation pattern for the application, the at least one implementation pattern providing context for the code;
automatically generating, via the computer processor, 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, wherein the application lineage data is generated during the build process and based on the one or more predefined annotation markers;
maintaining and storing, via the computer processor, the registry information in the memory component;
generating, via the computer processor, analytics based on the registry information; and
providing, via an interactive interface, a search function, a filtering function, and visualization data that graphically depicts the application lineage data comprising ownership traceability information.
14. The computer readable medium of claim 13 , wherein the build process is initiated by a continuous integration and continuous delivery pipeline.
15. The computer readable medium of claim 13 , wherein the registry information comprises asset inventory and metadata that represents ownership and traceability.
16. The computer readable medium of claim 13 , wherein the plurality of logical and physical catalogs comprise one or more of: API catalog, microservices catalog, applications catalog, events catalog, data catalog, metadata catalog, infrastructure catalog and configurations catalog.
17. The computer readable medium of claim 13 , wherein the one or more assets or services of an ecosystem comprise Application assets, Events assets, API assets and Data Assets.
18. The computer readable medium of claim 13 , wherein the visualization data is automatically generated and versioned each time the code is built.