A method and system for quickly retrieving service links and businesses under a microservice architecture

Abstract

The present invention belongs to the field of computer microservice technology, and provides a method and system for quickly retrieving service links and businesses under a microservice architecture. First, a set development specification framework is obtained. After the microservice is started, the current microservice is parsed and mapped based on the set development specification framework to obtain business data; then, a user search request is obtained, and a business method that meets the user search request is retrieved from the business data, and the link data of the microservice to which the business method belongs is obtained, thereby realizing the retrieval and display of various types of operation data in the microservice from the perspective of business terms.

Description

Technical Field

[0001] The present invention belongs to the field of computer microservice technology, and in particular to a method and system for quickly retrieving service links and businesses under a microservice architecture. Background Art

[0002] The statements in this section merely provide background information related to the present invention and do not necessarily constitute prior art.

[0003] The dependency link information between microservices is very important data for system designers, developers, testers, and operation and maintenance personnel, especially for large and complex distributed systems based on microservice architecture. It is very meaningful and necessary to study and analyze the tracking, analysis and retrieval mechanism of call dependency data between microservice modules in the microservice architecture, make the tracking and retrieval of service link data more efficient, and maximize the work efficiency of designers, developers, testers and operation and maintenance personnel of information systems under the microservice architecture.

[0004] In order to achieve link tracking collection, Google released the distributed link tracking system Dapper. The technical solution proposed by Dapper can well build a microservice link tracking data model and can well identify the call dependency relationship between microservices. The distributed link data collection and retrieval technical solution based on Google's Dapper theory can easily collect the microservice name, business method name, parameter name and parameter value, business method execution time, and related microservice link data involved in each access request through the processing of technical details such as tracking, transmission, collection, storage and display. Even the optimized technical solution can synchronously collect and display the operation log data of each microservice business method.

[0005] However, all the above data are technical abstract data for technical personnel, such as microservice names, business method names, etc., which are abstract technical terms or code snippets such as UserService and addUserInfo. Users must clearly know the business service name or method name in the code corresponding to the current business problem in order to retrieve data more conveniently and quickly. This is very unfriendly to testers and operation and maintenance personnel, who cannot understand and master these technical details. Therefore, in reality, the cooperation and assistance of developers is often required to locate and analyze the problem more quickly, which is bound to increase the cost of human communication and reduce the efficiency of testing and operation and maintenance.

[0006] Moreover, the various technical data collected by the distributed link data collection and retrieval technology solution based on Google's Dapper theory are not even friendly to developers. When the system modules are simple, developers may use short-term memory to assist testers or operation and maintenance personnel to quickly retrieve problems. However, when the system's business becomes more and more complex, or the number of modules or projects involved in the development of developers increases, and the development cycle becomes longer, developers cannot quickly locate problems based on microservice names and code method names. In this case, developers often first find the corresponding engineering source code through the business scenario, and then find the corresponding microservice and business method name in the code by viewing the engineering source code, and then use visualization tools to retrieve and locate the call link data that occurs in the business scenario, which seriously affects the efficiency of problem troubleshooting and locating, and the accuracy of problem location and troubleshooting cannot be effectively guaranteed. Summary of the invention

[0007] In order to solve the technical problems existing in the above-mentioned background technology, the present invention provides a method and system for quickly searching service links and businesses under a microservice architecture, which realizes the retrieval and display of various operating data in microservices from the perspective of business terms.

[0008] In order to achieve the above object, the present invention adopts the following technical solution:

[0009] A first aspect of the present invention provides a method for quickly retrieving service links and services under a microservice architecture, which includes:

[0010] Get the set development specification framework. After the microservice is started, parse and map the current microservice based on the set development specification framework to obtain business data.

[0011] A user search request is obtained, a business method that meets the user search request is retrieved from the business data, and link data of the microservice to which the business method belongs is obtained.

[0012] Furthermore, the link data is real-time data dynamically collected using Dapper's dynamic collection technology.

[0013] Furthermore, the business data includes microservice attribute data, knowledge data, technical data, and association mapping between the knowledge data and the technical data.

[0014] Furthermore, the method for obtaining the business data is:

[0015] After the microservice is started, read the microservice configuration items and parse to obtain the microservice attribute data;

[0016] The scanning thread obtains the implementation class object of the top-level class in the current microservice, and obtains all business methods of each implementation class;

[0017] Parse the API description information annotations on each business method to obtain knowledge data;

[0018] Parse the request mapping information annotation on each business method to obtain technical data;

[0019] Establish an associative mapping between the obtained knowledge data and technical data.

[0020] A second aspect of the present invention provides a rapid retrieval system for service links and businesses under a microservice architecture, which includes:

[0021] Link data storage module, used to store link data of all microservices;

[0022] The business data collection module obtains the set development specification framework. After the microservice is started, it parses and maps the current microservice based on the set development specification framework to obtain business data.

[0023] Business data storage module, connected to the business data collection module, is used to store the business data of all microservices;

[0024] The retrieval module is connected to the link data storage module and the business data storage module, and is used to obtain a user retrieval request, retrieve a business method that meets the user retrieval request from the business data, and obtain the link data of the microservice to which the business method belongs.

[0025] Furthermore, it also includes a visualization module for displaying the business data of the business method that meets the user's search request and the link data of the microservice to which the business method belongs.

[0026] Furthermore, it also includes a link data collection module, which is used to dynamically collect real-time link data using Dapper's dynamic collection technology and transmit it to the link data storage module.

[0027] Furthermore, the business data includes microservice attribute data, knowledge data, technical data, and association mapping between the knowledge data and the technical data.

[0028] A third aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the method for quickly retrieving service links and businesses under the microservice architecture as described above.

[0029] The fourth aspect of the present invention provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps in the method for rapid retrieval of service links and businesses under the microservice architecture as described above are implemented.

[0030] Compared with the prior art, the present invention has the following beneficial effects:

[0031] The present invention provides a method for quickly retrieving service links and businesses under a microservice architecture. Through a unified coding specification, it ensures that the microservice business methods in the source code of the microservice module have a unified method annotation format, so that the business methods in the source code of each microservice module in the entire system and the corresponding business term mapping relationship data can be automatically collected, thereby realizing a data visualization system based on business knowledge data.

[0032] The present invention provides a method for quickly retrieving service links and businesses under a microservice architecture, which realizes data visualization based on business knowledge; it enables system testers and operation and maintenance personnel to conveniently, quickly and efficiently complete the location and tracking of common business problems without having to master any technical details or rely on the assistance of developers, thereby improving the efficiency of testing and operation and maintenance and saving human communication costs; it enables developers to directly and conveniently troubleshoot and locate problems found in development from a business perspective without having to remember the mapping information between code methods and business terms, thereby reducing the burden on developers and improving development efficiency.

[0033] The present invention provides a method for rapid retrieval of service links and businesses under a microservice architecture, which realizes data visualization based on business knowledge, and can invisibly make system developers, testers, and operation and maintenance personnel pay more attention to business domain knowledge, and consciously use business domain terms for communication and problem analysis more frequently in daily life, which is conducive to the construction of a system for rapid response of enterprises to customer business needs, making communication between various personnel of the enterprise and customers smoother, and improving customer satisfaction. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The accompanying drawings in the specification, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0035] Figure 1 It is a schematic diagram of the complex calling relationship between microservices;

[0036] Figure 2 It is a data model diagram based on Google-Dapper's dynamic dependency analysis technology;

[0037] Figure 3 This is an overall flow chart of a method for quickly searching service links and businesses under a microservice architecture according to a first embodiment of the present invention;

[0038] Figure 4 This is a flow chart of collecting business data in Embodiment 1 of the present invention;

[0039] Figure 5 This is a core class diagram of the microservice development specification of the first embodiment of the present invention;

[0040] Figure 6 It is an overall framework diagram of a rapid retrieval system for service links and businesses under a microservice architecture according to the second embodiment of the present invention. DETAILED DESCRIPTION

[0041] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0042] It should be noted that the following detailed descriptions are all illustrative and intended to provide further explanation of the present invention. Unless otherwise specified, all technical and scientific terms used herein have the same meanings as those commonly understood by those skilled in the art to which the present invention belongs.

[0043] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit exemplary embodiments according to the present invention. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprising" and / or "including" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.

[0044] Terminology explanation section:

[0045] The microservice architecture designs the traditional single application into a set of independent, small service modules. The service modules coordinate and cooperate with each other, and the services collaborate with each other using lightweight communication mechanisms (usually RESTful API based on HTTP protocol). Each service module is built around the most suitable technology stack for the specific business and can be independently deployed in the production environment. As the business requirements of the system become more and more complex, a large information system designed with the microservice architecture may have dozens or even hundreds of microservices in the background to support a seemingly simple business scenario. The more microservices the system is split into, the more complicated the call chain dependencies between services in this distributed service architecture will naturally become. For example, Figure 1 shown.

[0046] Dapper, a distributed link tracking system, explains the concept, data representation, tracking, transmission, collection, storage and display of link tracking in distributed systems, especially in microservice architecture, and proposes the concepts of Trace and Span: The meaning of Trace is relatively intuitive, which is the call link, referring to the path of a front-end request through all back-end microservices. Each link is identified by a globally unique TraceID; Span represents the intermediate service node in the call link. Each Span has a unique identifier SpanID, and there is a parent-child relationship between Spans. The upstream Span is the parent Span of the downstream (identified by ParentID). In this way, each Span has two identifiers, SpanID and ParentID, which respectively identify the identifier of the current Span and the Span identifier of its parent node. SpanID is unique in a link. Dapper dynamically produces the structural data of the above data model through tracking technology during the service operation process, and stores these data in a unified manner, so that each service call link information can be collected, such as Figure 2 shown.

[0047] Embodiment 1

[0048] like Figure 3 As shown, this embodiment provides a method for quickly searching service links and businesses under a microservice architecture, which mainly includes the following steps:

[0049] Step 1: Get the development specification framework you want.

[0050] As an implementation method, Figure 5 As shown, the core classes of the development specification framework include the top-level class BaseController, the API description information annotation class ApiOperation, and the request mapping information annotation class RequestMapping.

[0051] BaseController: It is the top-level class of all microservice implementation classes. All microservice classes must inherit from this class. A unified top-level class is designed to facilitate the unified extraction of microservice knowledge data. The efficiency of knowledge data collection can be improved through filtering of the top-level class.

[0052] ApiOperation: It is the functional description annotation class of the business method of the microservice implementation class. All microservice business methods provided to the outside world in the system must be marked with this annotation. The annotation class contains two attributes, value and notes. The value attribute represents the abbreviation of the business operation corresponding to the microservice method, such as "view project details"; the notes attribute represents the detailed description of the business operation, such as "query project information in the personal portal system based on transaction category, state-owned status, project status, and provincial and municipal information". By scanning this annotation, you can obtain the business knowledge information of the microservice.

[0053] RequestMapping: It is the access address mapping information annotation class of the business method of the microservice implementation class. All microservice business methods provided to the outside world in the system must be marked with this annotation. The annotation class contains two attributes, value and method. The value attribute specifies the URL address information exposed by the business method to the outside world; the method attribute specifies the http method published by the microservice, such as get, post, put, delete, etc. By scanning this annotation, you can obtain the URL, HttpMethod and other technical information published by the microservice business method. Combined with the ApiOperation annotation, you can collect the mapping data of the technical information and knowledge information of the microservice business method.

[0054] The development framework specification technically guarantees that the developed microservices comply with the corresponding design conventions, and provides technical guarantees for the correct implementation of the microservice link and business knowledge data collection method proposed in the present invention. The method of uniformly using @ApiOperation annotations and @RequestMapping annotations to mark microservice business methods mentioned in this implementation example is only an implementation example of the unified coding specification. Any other annotation methods, even custom annotation methods, fall within the scope of protection of the present invention's patent.

[0055] Step 2, link data collection: After the microservice is started, the link data of the microservice is collected. Link data is real-time data dynamically collected using Google's Dapper dynamic collection technology. The link data includes the call link of the microservice, the module dependency on the call link, the module running time, and the module running log.

[0056] Step 3, business data collection: After the microservice is started, the current microservice is parsed and mapped to obtain business data based on the set development specification framework. Business data includes microservice attribute data, knowledge data, technical data, and the association mapping between knowledge data and technical data. Figure 4 As shown, the following steps are included:

[0057] (1) After the microservice is started, start the scanning thread and read the microservice configuration items, specifically read the spring.application.desc and spring.application.name configuration items, and parse to obtain the microservice attribute data. The microservice attribute data includes the name of the microservice and the business name (that is, the name of each business method in the microservice). Preferably, the name of the microservice is an English name, such as usermanager-user management.

[0058] (2) The scanning thread first obtains all subclass objects of the top-level class (BaseController class) in the current microservice, that is, various microservice implementation class objects; then, it traverses each implementation class according to the following process:

[0059] (2-1) Get all business methods of the implementation class;

[0060] (2-2) Get the API description information annotation (@ApiOperation annotation) on each business method;

[0061] Specifically, obtain the value and notes attributes in the @ApiOperation annotation, and parse to obtain business knowledge data such as the business operation term abbreviation and detailed description of the business method;

[0062] (2-3) Get the request mapping information annotation (@RequestMapping annotation) of the business method;

[0063] Specifically, get the value and method attributes of the @RequestMapping annotation, and parse to get the url, httpmethod and other technical data of the business method;

[0064] (2-4) Establish an association mapping between the acquired business knowledge data and technical data of the business method.

[0065] Among them, the @ApiOperation annotation and the @RequestMapping annotation for marking microservice business methods are just an example of implementing the unified coding protocol of the present invention. Any other annotation method, even a custom annotation method, can be used.

[0066] (3) The English name and business name of the microservice, as well as the knowledge data, technical data and their associated mappings of all business methods in the microservice are saved in the persistence layer.

[0067] As an implementation method, the persistence layer is a MySQL database, a NoSQL database or other relational database.

[0068] Step 4: Obtain the user's search request. Based on the user's search request, retrieve the business method that meets the user's search request in the business data, and extract the link data of the microservice to which the business method belongs.

[0069] Specifically, obtain the user's search request, and based on the user's search request, search the knowledge data and technical data in the persistence layer to obtain the business method that matches the user's search request, and obtain the microservice to which the business method belongs and the call link of the microservice, and obtain and display the business data that meets the user's search request and the call link of the related microservices.

[0070] The user search request is the abbreviation or detailed description of the business term.

[0071] When displaying and querying microservice call link data, the mapping data of business knowledge and technical data obtained through the above process, and then through the collected microservice call link data, can be used to quickly, efficiently and accurately retrieve relevant operation data on the microservice call link by retrieving the abbreviation or detailed description of business terms, so that testers, operation and maintenance personnel and developers can quickly respond to and locate problems.

[0072] Embodiment 2

[0073] like Figure 6 As shown, this embodiment provides a rapid retrieval system for service links and businesses under a microservice architecture, which specifically includes the following modules: a microservice encoding protocol module, a link data collection module, a link data storage module, a business data collection module, a business data storage module, a retrieval module and a visualization module.

[0074] The microservice coding specification module is used to obtain the set development specification framework, provides a unified top-level parent class design for the microservice extension method, and stipulates that the microservice business method must use a unified annotation class to mark knowledge data such as business terms, as well as technical data such as url and HttpMethod; the microservice development method, especially the code annotation method, is uniformly specified to facilitate the unified collection of business data by the business data collection module, which is the technical basis and guarantee of the present invention.

[0075] The link data collection module is used to dynamically collect real-time link data using Google's Dapper dynamic collection technology after the microservice is started. The link data collection module is responsible for collecting link technical data such as the microservice call link, module dependencies on the microservice call link, module running time, and module running log.

[0076] The link data storage module is connected to the link data collection module and is used to store the link data of all microservices.

[0077] The business data collection module is used to parse and map the current microservice to obtain business data based on the set development specification framework after the microservice is started. The business data includes microservice attribute data, knowledge data, technical data, and the association mapping between knowledge data and technical data.

[0078] The business data collection module is responsible for collecting the business knowledge data of the logical mapping of the method name of the service published by each microservice and the business name corresponding to the method, so as to facilitate the data visualization module to visualize and display the data from the perspective of business terminology; scan and analyze the top-level classes and annotation classes to obtain the business knowledge data and technical data of the microservice business methods, and establish mapping information for the two types of data and save it to the business data storage module.

[0079] The business data storage module is connected to the business data collection module and is used to store the business data of all microservices.

[0080] The retrieval module connects the link data storage module and the business data storage module, and is used to retrieve the business method that meets the user's retrieval request in the business data based on the user's retrieval request, and obtain the link data of the microservice to which the business method belongs.

[0081] According to the technical data and business knowledge data collected by the link data collection module and the business data collection module, and the mapping data between them, various types of operation data of the microservice system are retrieved and displayed from the perspective of business terms. Based on the mapping relationship data between the microservice business method technical data and the business knowledge data, and combined with the link data information collected by the microservice link data collection module, a new display method is provided to query and display the relevant information data on the microservice call link from the perspective of business term abbreviations or detailed descriptions, so that testing and operation and maintenance personnel only need to master business knowledge without understanding and mastering any technical details to query and locate the system operation data.

[0082] The visualization module is used to display the business data of the business method that meets the user's search request and the link data of the microservice to which the business method belongs.

[0083] It should be noted here that each module in this embodiment corresponds to each step in Example 1 one by one, and the specific implementation process is the same, which will not be repeated here.

[0084] Embodiment 3

[0085] This embodiment provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps in the method for quickly retrieving service links and businesses under the microservice architecture as described in the first embodiment above are implemented.

[0086] Embodiment 4

[0087] This embodiment provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the processor implements the steps in the method for quickly retrieving service links and businesses under the microservice architecture as described in the first embodiment above.

[0088] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.

[0089] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0090] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0091] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0092] A person skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0093] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for quickly retrieving service links and businesses under a microservice architecture, characterized in that: include: Get the set development specification framework. After the microservice is started, parse and map the current microservice based on the set development specification framework to obtain business data. Obtain a user search request, retrieve a business method that meets the user search request from the business data, and obtain link data of the microservice to which the business method belongs; The established development specification framework automatically collects business methods and corresponding business term mapping relationship data in the microservice module source code through unified coding specifications; After the microservice is started, read the microservice configuration items and parse to obtain the microservice attribute data; The scanning thread obtains the implementation class object of the top-level class in the current microservice, and obtains all business methods of each implementation class; Parse the API description information annotations on each business method to obtain knowledge data; Parse the request mapping information annotation on each business method to obtain technical data; Establish association mapping between the obtained knowledge data and technical data; The link data is real-time data dynamically collected using Dapper's dynamic collection technology; Displays the business data of the business method that meets the user's search request and the link data of the microservice to which the business method belongs.

2. The method for quickly retrieving service links and businesses under the microservice architecture according to claim 1, characterized in that: The business data includes microservice attribute data, knowledge data, technical data, and association mapping between the knowledge data and the technical data.

3. A system for quickly retrieving service links and businesses under a microservice architecture, which executes a method for quickly retrieving service links and businesses under a microservice architecture as claimed in claim 1, characterized in that: include: Link data storage module, used to store link data of all microservices; The business data collection module obtains the set development specification framework. After the microservice is started, it parses and maps the current microservice based on the set development specification framework to obtain business data. Business data storage module, connected to the business data collection module, is used to store the business data of all microservices; A retrieval module, connected to the link data storage module and the business data storage module, is used to obtain a user retrieval request, retrieve a business method that meets the user retrieval request from the business data, and obtain the link data of the microservice to which the business method belongs; The visualization module is used to display the business data of the business method that meets the user's search request and the link data of the microservice to which the business method belongs.

4. The rapid retrieval system for service links and businesses under the microservice architecture as described in claim 3 is characterized in that: It also includes a link data collection module connected to the link data storage module.

5. The rapid retrieval system for service links and businesses under the microservice architecture as described in claim 3 is characterized in that: The business data includes microservice attribute data, knowledge data, technical data, and association mapping between the knowledge data and the technical data.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps in the method for quickly retrieving service links and businesses under the microservice architecture as described in any one of claims 1-2 are implemented.

7. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps in the method for quickly retrieving service links and businesses under the microservice architecture as described in any one of claims 1-2 are implemented.

Images