Dependence management method and device based on graphic database

Abstract

The invention provides a dependence management method and device based on a graphic database, and belongs to big data. The method comprises the steps that software component packages are imported into a node structure of the graphic database; establishing a software component package dependence relationship data set according to the dependence relationship between the software component packages and the node structure of the graphic database; establishing a management interface for the graphic database, and managing the dependency relationship data set of the software component package. According to the dependence management method based on the graphic database, the defects of an existing dependency management scheme can be overcome, the purpose of conveniently and rapidly managing the dependent rule extraction application program is achieved, and the method has flexibility, expansibility and certain automation and intellectualization.

Description

technical field [0001] The invention relates to the technical field of computer data processing, in particular to a graph database-based dependency management method and device. Background technique [0002] This section is intended to provide a background or context for implementations of the invention that are recited in the claims. The descriptions herein are not admitted to be prior art by inclusion in this section. [0003] Usually, in software development, it is necessary to rely on external components and toolkits (mysql, JQuery, AngularJS, etc.), and these dependent libraries should use tools for dependency management instead of manual download and maintenance. [0004] The prior art adopts a Maven-based dependency management method, and all dependencies are determined by detecting the dependency transfer through the analysis of the package and the single dependency of the package. The main steps are as follows: configure all the direct dependencies required by the...

AI Technical Summary

Problems solved by technology

[0005] However, this Maven-based dependency management method is too simple and crude for dependency management, not flexible enough, and cannot identify repeated dependencies (for example: both component packages a and b depend on component package c, resulting in repeated loading of c) and Dependency conflicts (at least two identical component packages are dependent but different versions) and other issues

[0006] Once the repeated dependencies and conflicts of component packages occur, it is a heavy workload to solve (need to reorganize and check the dependencies), and often require manpower to repair software problems. The cost of manpower is high, and it does not meet the requirements of flexibility and scalability.

Images