Converged storage method of service source data

Abstract

The invention discloses a converged storage method of service source data. The method comprises the following steps of acquiring the service source data; defining a storage mode of the document storage database-based service source data; defining a storage mode of the graphics database-based service source data; reading a service source log, and according to the service source log, creating and updating a document storage database; reading documents in the document storage database according to periods, inserting the documents into a graphics database, and creating a source graph spectrum; according to the document storage database, updating the graphics database. According to the converged storage method of the service source data provided by the invention, balance between a multi-type search requirement and search efficiency is realized; the transparency is kept, the using experience of a user is improved, and uniform analysis and search operation are facilitated through a uniform search analyzer.

Description

technical field [0001] The present invention relates to the technical field of cloud service storage, in particular to a service origin fusion storage method. Background technique [0002] Service origin is different from ordinary system logs. It describes the detailed behavioral characteristics of services, including real-time dependencies of services, service execution time, input and output, etc. For details, see patent 201410323340.8. Commonly used storage methods, for example, use relational Database storage, a large amount of detailed service behavior data is stored in a single table, which cannot support fast and efficient service query operations, nor can it support service tracking. The non-relational database represented by Mongodb has the characteristics of free mode, and stores data in the form of key-value, which is convenient for data aggregation operation, but cannot support tracking query. The graph database represented by Neo4j can store service dependenc...

AI Technical Summary

Problems solved by technology

[0002] Service origin is different from ordinary system logs. It describes the detailed behavior characteristics of services, including real-time dependencies of services, service execution time, input and output, etc. For details, see patent 201410323340.8. Commonly used storage methods, for example, use relational Database storage, a large amount of detailed service behavior data is stored in a single table, which cannot support fast and efficient service query operations, nor service tracking

The non-relational database represented by Mongodb has the characteristics of free mode, and stores data in the form of key-value, which is convenient for data aggregation operation, but cannot support tracking query

The graph database represented by Neo4j can store service dependencies in the database in the form of graphs, which is convenient for querying service dependencies, but a large amount of service behavior details are stored in relational attributes, which is not conducive to fast aggregation operations

Images