WO2022134358A1

WO2022134358A1 - Microservice data processing method, apparatus, microservice processing platform, and medium

Info

Publication number: WO2022134358A1
Application number: PCT/CN2021/084251
Authority: WO
Inventors: 曾海桑; 郭志坚; 汪培; 白云飞
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-12-24
Filing date: 2021-03-31
Publication date: 2022-06-30
Also published as: CN112738060B; CN112738060A

Abstract

The present application is suitable for the technical field of big data and provides a microservice data processing method, an apparatus, a microservice processing platform, and a medium. The method comprises: determining a target registration center containing registration information for a microservice and a target registration type of the target registration center; generating a target call interface in a microservice registration adaptation engine of a microservice processing platform according to the target registration type; obtaining microservice data of a microservice according to the target call interface and a target open interface; and writing the microservice data into a database of the microservice processing platform and performing centralized processing. Utilizing the described method to obtain microservice data of various microservices by means of performing interface adaptation with registration centers of different registration types, an effect of performing effective processing directly on a plurality of pieces of microservice data when pieces of registration information for a plurality of microservices are respectively deployed on registration centers of different registration types can be achieved.

Description

Microservice data processing method, device, microservice processing platform and medium

This application claims the priority of the Chinese patent application with the application number 202011556562.6 and the invention titled "Microservice Data Processing Method, Device, Microservice Processing Platform and Medium" filed in the China Patent Office on December 24, 2020, The entire contents of which are incorporated herein by reference.

technical field

The present application belongs to the technical field of big data, and in particular, relates to a method, device, microservice processing platform and medium for processing microservice data.

Background technique

In the prior art, when the registration information of multiple microservices are respectively deployed in registration centers of different registration types, it is difficult to directly process the multiple microservices through a separate microservice processing platform due to the different registration types of the registration centers. At present, the registration information of a large number of microservices is usually deployed in the registry of the same registration type. However, the inventor realizes that if a large number of microservices already have corresponding registration centers, the registration information deployed by the microservices in the corresponding registration centers needs to be deleted. After that, redeploy the registration information in the registration center of the same registration type. In this case, when the registration information is redeployed, the workload of the staff will be increased. Therefore, at present, when the registration information of multiple microservices are respectively deployed in the registration centers of different registration types, it is difficult to directly and effectively process the data of multiple microservices through a separate microservice processing platform.

technical problem

One of the purposes of the embodiments of the present application is to provide a microservice data processing method, device, microservice processing platform and medium, which aims to solve the problem when the registration information of multiple microservices are respectively deployed in registration centers of different registration types , the technical problem that it is difficult to directly and effectively process the data of multiple microservices through a single microservice processing platform.

technical solutions

In order to solve the above-mentioned technical problems, the technical solutions adopted in the embodiments of the present application are:

A first aspect of the embodiments of the present application provides a method for processing microservice data, which is applied to a microservice processing platform, and the method includes:

Determine the target registry that contains the registration information of the microservice, and determine the target registration type of the target registry;

According to the target registration type, in the microservice registration adaptation engine of the microservice processing platform, a target call interface adapted to the target open interface of the target registry is generated;

Acquire the microservice data of the microservice according to the target calling interface and the target open interface;

The microservice data is written into the database of the microservice processing platform, and the microservice data is centrally processed, and the database contains microservice data corresponding to multiple microservices one-to-one.

A second aspect of the embodiments of the present application provides an apparatus for processing microservice data, which is applied to a microservice processing platform, and the apparatus includes:

The first acquisition module is used to determine the target registration center containing the registration information of the microservice, and to determine the target registration type of the target registration center;

A generation module, configured to generate a target call interface adapted to the target open interface of the target registry in the microservice registration adaptation engine of the microservice processing platform according to the target registration type;

A second acquisition module, configured to acquire the microservice data of the microservice according to the target call interface and the target open interface;

A processing module, configured to write the microservice data into the database of the microservice processing platform, and centrally process the microservice data, where the database contains microservice data corresponding to multiple microservices one-to-one .

A third aspect of the embodiments of the present application provides a microservice processing platform, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the When a computer program realizes:

A fourth aspect of the embodiments of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement:

A fifth aspect of the embodiments of the present application further provides a computer program product, when the computer program product runs on the microservice processing platform, the microservice processing platform can realize in real time:

beneficial effect

Compared with the prior art, the embodiments of the present application include the following advantages:

In the embodiment of the present application, after determining the target registry corresponding to the microservice and the target registration type of the target registry, the microservice processing platform only needs to adapt the target open interface of the existing target registry. So that the microservice processing platform can be connected with the target registry, so that the registration information of the microservice deployed in the target registry can be obtained. After that, the microservice data of the corresponding microservice can be obtained according to the registration information for processing. Based on this, the microservice processing platform can not only uniformly process the microservice data of multiple microservices corresponding to registries of different registration types, but also effectively reduce the workload of the staff and reduce the need for re-engineering in the microservice processing platform. The risk of microservice data leakage when deploying registration information.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the accompanying drawings that are used in the description of the embodiments or exemplary technologies. Obviously, the drawings in the following description are only for the present application. In some embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without any creative effort.

FIG. 1 is an implementation flowchart of a method for processing microservice data provided by an embodiment of the present application;

FIG. 2 is an implementation flowchart of a method for processing microservice data provided by another embodiment of the present application;

3 is an implementation flowchart of a method for processing microservice data provided by yet another embodiment of the present application;

FIG. 4 is an implementation flowchart of a method for processing microservice data provided by another embodiment of the present application;

5 is an implementation flowchart of a method for processing microservice data provided by another embodiment of the present application;

6 is a schematic diagram of an implementation of S10CA of a method for processing microservice data provided by an embodiment of the present application;

7 is a schematic diagram of an implementation of S10CB of a method for processing microservice data provided by an embodiment of the present application;

8 is a structural block diagram of an apparatus for processing microservice data provided by an embodiment of the present application;

FIG. 9 is a structural block diagram of a microservice processing platform provided by an embodiment of the present application.

Embodiments of the present invention

In the following description, for the purpose of illustration rather than limitation, specific details such as a specific system structure and technology are set forth in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be practiced in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It is to be understood that, when used in this specification and the appended claims, the term "comprising" indicates the presence of the described feature, integer, step, operation, element and/or component, but does not exclude one or more other The presence or addition of features, integers, steps, operations, elements, components and/or sets thereof.

It will also be understood that, as used in this specification and the appended claims, the term "and/or" refers to and including any and all possible combinations of one or more of the associated listed items.

In addition, in the description of the specification of the present application and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the description, and should not be construed as indicating or implying relative importance.

The microservice data processing method provided by the embodiment of the present application is applied to a microservice processing platform. Among them, the microservice processing platform includes a unified registry, a microservice registration adaptation engine, a microservice monitoring engine, and a database. The above unified registration center can be used to deploy the registration information of each microservice, so that each newly launched microservice does not need to deploy its own registration information in multiple registration centers, and realizes the centralized processing of registration information of multiple microservices . The above microservice registration adaptation engine is used to adapt the interface to the existing registration center of the microservice, so that the microservice processing platform can obtain the registration information of the microservice from the existing registration center through this interface, and obtain the registration information according to the registration information. Microservice data for this microservice. The above-mentioned microservice monitoring engine can be used to call a toolkit adapted to the frame type to access the microservice framework after determining the frame type of the microservice framework in the microservice, so as to implement the invocation of the microservice component in the microservice. The above database can be used to store the microservice data of each microservice, the monitoring data generated by the microservice when the microservice is running, and the analysis results obtained by analyzing the monitoring data, which are not limited thereto.

Please refer to FIG. 1. FIG. 1 shows an implementation flowchart of a method for processing microservice data provided by an embodiment of the present application. The method is applied to a microservice processing platform, and the method specifically includes the following steps:

S101. Determine a target registration center containing registration information of a microservice, and determine a target registration type of the target registration center.

In an application, the above-mentioned microservice is an architectural solution for building a service application. Among them, the architectural solution of the service application is different from the traditional monolithic solution, and the service application can be divided into multiple core service functions. Each service function can be called a service and can be built and deployed separately, that is, each service function can be considered a microservice. Among them, when each microservice is started, data information such as the network address of the microservice and the microservice component needs to be registered in the registration center, and the registration center will store it. Based on this, when calling a microservice, the service consumer can query the network address of the microservice from the registry. After that, the microservice component is obtained through the network address, and is connected to the calling interface for accessing the microservice to call the microservice component.

In the application, whether the microservice has a corresponding target registry and the target registration type of the target registry can be determined by the staff according to the actual situation, and the determination result is sent to the microservice processing platform.

In an application, there are various registration types of the above-mentioned registration center. Specifically, the registration types include but are not limited to Zookeeper type and Eureka type. It is understandable that for different microservices, the registration type of the registry used may be the same or different. It is understandable that if the registration types of the microservices corresponding to the registry are different, it is difficult for the microservice processing platform of each microservice to be compatible with the registration centers of other registration types. Furthermore, it is difficult to uniformly process microservices corresponding to multiple different registration types.

S102. According to the target registration type, in the microservice registration adaptation engine of the microservice processing platform, generate a target calling interface adapted to the target open interface of the target registration center.

In the application, the above has explained that when each microservice is started, it is necessary to deploy the data information such as the network address of the first microservice and the microservice components in the registration center. It can be considered that after the above-mentioned microservice registration adaptation engine is adapted and connected to the target registration center, data information such as network addresses and microservice components respectively corresponding to deployment of all microservices in the target registration center can be obtained. Based on this, in order to realize the adaptation connection between the microservice registration adaptation engine and the registry, it is necessary to obtain the open interface of the target registry. After that, the microservice registration adaptation engine adapts the target registry according to the open interface, and generates a target calling interface that can transmit data with the target registry. Wherein, the above-mentioned calling interface and open interface can both be API interfaces. It should be noted that the above-mentioned microservice registration adaptation engine is a component in the microservice processing platform, and its function is to adapt the open interfaces provided by the registration centers of different registration types, and generate registration centers corresponding to each registration type. call interface.

It is understandable that a component (registry center) has an open API, which means that the component can open its own data (data in the registry center) to the outside world. At this time, the open API interface includes the usage authority of the API interface, for example, the number of times of calling the API interface, the calling object, and the like.

S103. Acquire microservice data of the microservice according to the target calling interface and the target open interface.

S104. Write the microservice data into a database of the microservice processing platform, and perform centralized processing on the microservice data, where the database includes microservice data corresponding to multiple microservices one-to-one.

In the application, the above microservice data can be understood as data information such as the network address of the microservice and the microservice components. It should be noted that when the target invocation interface of the microservice registration adaptation engine is adapted to the target open interface of the target registry, the microservice processing platform can invoke the target invocation interface to connect with the target open interface. Furthermore, data information such as the network address of the microservice and the components of the microservice can be searched in the target registry.

In the application, after the microservice data is obtained, the microservice data needs to be written into the database of the microservice processing platform for preservation. In this way, after the database contains the microservice data corresponding to the multiple microservices one-to-one, the centralized processing of the multiple microservice data can be realized. Among them, the above centralized processing may be to set the identification information of each microservice data separately to distinguish each microservice, and perform processing such as adding, deleting, modifying and querying the registration information deployed by each microservice in the target registration center. This is not limited.

In this embodiment, after determining the target registry corresponding to the microservice and the target registration type of the target registry, the microservice processing platform only needs to adapt the target open interface of the existing target registry. So that the microservice processing platform can be connected with the target registry, so that the registration information of the microservice deployed in the target registry can be obtained. After that, the microservice data of the corresponding microservice can be obtained according to the registration information for processing. Based on this, the microservice processing platform can not only uniformly process the microservice data of multiple microservices corresponding to registries of different registration types, but also effectively reduce the workload of the staff and reduce the need for re-engineering in the microservice processing platform. The risk of microservice data leakage when deploying registration information.

Referring to FIG. 2, in one embodiment, the target registry includes the unified registry of the microservice processing platform and the existing registry of the microservice; at S101, the target registry that includes the registration information of the microservice is determined Before, it also includes the following steps S101A-S101B, which are detailed as follows:

S101A. If the microservice does not have a corresponding registration center, obtain registration information of the microservice, and deploy the registration information in the unified registration center.

In an application, the above unified registration center may be a registration center pre-set by the staff in the microservice processing platform, which may be used to deploy registration information for microservices that do not have a corresponding registration center.

In an application, for a newly launched microservice, it usually does not have a corresponding registry. Based on this, the registration information of the microservice can be deployed in the unified registration center in the microservice processing platform. At this time, there is only one unified registration center, that is, there is only one registration type of the unified registration center. At this point, the unified registry is the target registry, and both the unified registry and the microservice registration adaptation engine are components in the microservice processing platform. It can be considered that the microservice registration adaptation engine already has a target calling interface adapted to the target open interface of the unified registry. Therefore, deploying the registration information of the newly launched microservices in the unified registry can unify the registry types corresponding to the newly launched microservices, avoid building a registry of multiple registration types in the microservice processing platform, and reduce the processing of microservices. Component resources required to be used in the platform.

S101B. If the microservice already has a corresponding registration center, determine the registration center corresponding to the microservice as the target registration center of the microservice.

In the application, for a microservice that has a corresponding registry, at this time, it can be determined that the existing corresponding registry is the target registry. Based on this, the methods of S101 to S102 above can be used to perform interface adaptation on the target open interface of the target registry by using the microservice registration adaptation engine.

In this embodiment, after it is determined that the microservice has a corresponding registration center, the interface adaptation of the existing registration center is performed by using the above S101 to S102 to obtain the microservice data of the microservice, and it is not necessary to perform the interface adaptation of the microservice. The registration information is redeployed to reduce the workload of the staff; and after it is determined that the microservice does not have a corresponding registration center, use the unified registration center of the same registration type to deploy the registration information of each microservice, which can avoid the need for microservices. A registry of multiple registration types is built in the processing platform to reduce the component resources required in the microservice processing platform.

3, in an embodiment, before S101 determines the target registry containing the registration information of the microservice, the following steps S101C-S101D are further included, which are described in detail as follows:

S101C, if the microservice already has a corresponding registry, delete the registration information deployed by the microservice in the existing corresponding registry.

S101D: Acquire registration information of the microservice, and redeploy the registration information in the unified registration center.

In the application, after it is determined that the microservice has a corresponding registry, the registration information deployed by the microservice in the existing corresponding registry can also be deleted. After that, the registration information of the microservice is re-deployed in the unified registry. It should be noted that when the number of microservices that already have a corresponding registry is small, the registration information can be re-deployed in the above manner to reduce the interface adaptation between the microservice registration adaptation engine and the external registry. quantity.

Referring to FIG. 4 , in an embodiment, after the microservice data is written into the database of the microservice processing platform in S104, and the microservice data is centrally processed, the following steps S104A-S104C are further included. as follows:

S104A. Determine the framework type of the microservice framework used by the microservice.

In an application, the above microservice framework can be used to deploy the runtime environment required by the microservice at runtime. Therefore, when generating microservices, it is necessary to build the microservice framework of the microservice in advance, so as to deploy various service functions of the microservice in the microservice framework, so that the microservice can run normally. Because the service functions of different microservices are different, the framework types of the microservice framework used are also different. The above frame types include but are not limited to Service Mesh frame types, Linkerd frame types, and the like.

It should be noted that the method for determining the frame type of the microservice framework can be consistent with the method for determining the target registration type of the target registry. For example, it can be determined by the staff according to the actual situation of the microservice, and the determination result is sent to the microservice processing platform, which is not limited.

S104B, calling a toolkit adapted to the framework type through the microservice monitoring engine of the microservice processing platform.

S104C. When running the microservice, access the microservice framework of the microservice according to the toolkit to invoke the service component of the microservice.

In the application, after obtaining the microservice data of the microservice, in order to run the microservice (that is, calling the microservice component in the microservice data), it is necessary to deploy the corresponding microservice framework in the microservice processing platform. Based on this, in order not to deploy the microservice framework of each frame type in the microservice processing platform, the microservice processing platform can use the microservice monitoring engine to call the toolkit suitable for the framework type and the microservice framework to connect. Furthermore, the microservice processing platform can remotely access the microservice framework to realize the invocation of the microservice components. The above-mentioned microservice monitoring engine is a functional component in the microservice processing platform, which is used to store toolkits adapted to multiple framework types respectively, and can call the toolkit to adapt to the microservice framework of the corresponding frame type.

In an application, the above toolkit is a software development kit (Software Development Kit, SDK), which is generally a collection of development tools for building application software for a specific software package, software framework (microservice framework), operating system, and the like. That is, workers can install toolkits adapted to various framework types in the microservice monitoring engine in advance, so that the microservice processing platform can access the microservice framework.

In the prior art, microservices of different framework types usually have their own corresponding microservice processing platforms. In addition, due to different framework types, multiple microservice processing platforms are not compatible with each other. Based on this, the ability of the SDK toolkit to adapt to the microservices of various framework types can be used to connect with the microservice frameworks of various microservices, so as to realize the invocation and processing of microservices of different framework types.

Referring to FIG. 5 , in an embodiment, when the microservice is run in S104C, after accessing the microservice framework of the microservice according to the toolkit to invoke the service component of the microservice, the following steps are further included. S104CA-S104CC, detailed as follows:

S104CA: Obtain monitoring data when the microservice is running.

In the application, after the microservice processing platform is connected to the microservice framework through the SDK toolkit, the microservice component of the microservice can be called to run the microservice. Based on this, when the microservice is running, the microservice processing platform can obtain the monitoring data when the microservice is running. The above monitoring data includes, but is not limited to, the working hours of the microservice, processed processing data, and the like.

S104CB: Perform real-time integrated analysis on monitoring data within a preset time period to obtain an analysis result.

S104CC, store the analysis result in a database.

In an application, the above-mentioned time period may be a period preset by a user. The microservice processing platform can integrate the monitoring data in each time period, and then analyze it to obtain the analysis results. The above analysis result may be the work efficiency and work status of the microservice in the time period. By analyzing the running status of the microservices within a certain period of time, the staff can better adjust the microservice configuration of the microservices according to the analysis results of the microservices. The microservice configuration includes but is not limited to the running environment of the microservice and the functional components of the microservice.

In the application, the above database is a database for storing analysis results, which can store the analysis results in a graphical manner, so that the microservice processing platform can organize, plan, and analyze the disorganized analysis results (according to different time periods. Analyze the results again). Furthermore, the staff can adjust the configuration information of the microservices in real time according to the existing analysis results in the database.

Referring to FIG. 6 , in an embodiment, in S104CA acquiring the monitoring data of the microservice running time, the following sub-steps S104CA1-S104CA2 are further included, which are described in detail as follows:

S104CA1: Store the monitoring data of the microservice in the message queue of the microservice when the microservice is running.

S104CA2. Write the monitoring data in the message queue into the file system of the microservice processing platform through an asynchronous thread.

In the application, the above message queue is a temporary storage area in the microservice, which is used to store all the data (monitoring data) of the microservice in operation. The above-mentioned file system is a local file system in the microservice processing platform, wherein the file system can store the above-mentioned monitoring data persistently. In the actual process, when the microservice is running, problems such as crash and restart may occur. Based on this, if the microservice suddenly crashes during operation, the monitoring data stored in the message queue may be lost during the process of resuming the operation of the microservice. Therefore, after the data is stored in the local message queue of the microservice, the monitoring data in the message queue needs to be stored in the file system to prevent the loss of the monitoring data of the microservice.

In the application, the above thread refers to an execution flow in the process, which is used to execute the service in the microservice. The above asynchronous can be understood as a data transmission method. Specifically, when the monitoring data stored in the message queue is written into the file system by using an asynchronous thread, the monitoring data may not be processed synchronously between the microservice processing platform and the microservice. For example, the microservice saves the monitoring data to the message queue in real time, and the microservice processing platform can obtain the monitoring data within the time period from the message queue at preset time intervals, and save the monitoring data to the file system. In this way, the microservice processing platform and the microservice do not need to wait for each other's response, which improves the efficiency of data transmission. The above file system is specifically an HDFS system (distributed file system). Because the amount of data transmitted between the microservice processing platform and multiple microservices is very large, the HDFS system has the characteristics of high fault tolerance and can provide high throughput to obtain monitoring data in multiple microservices.

Referring to Fig. 7, in one embodiment, in S104CB, the monitoring data in the preset time period is subjected to real-time integrated analysis to obtain the analysis result, and in obtaining the analysis result, the following sub-steps S104CB1-S104CB3 are also included, which are described in detail as follows:

S104CB1. Perform data cleaning processing and data format conversion processing on the monitoring data in sequence to obtain processed monitoring data.

In applications, the above monitoring data is usually the raw data when the microservice is running, and the format and dimension of the raw data may vary. Based on this, it is necessary to perform data cleaning and format conversion processing on the monitoring data. Among them, the data cleaning process may be to clean up the data with transmission errors in the monitoring data. In an application, the monitoring data obtained above may be monitoring data in multiple formats such as double, int, and char. In order to facilitate subsequent analysis and processing, the data format of each monitoring data can be unified. Convert the current data format of the monitoring data to the data in the preset target format, which is not limited. At this point, the data in the target format is the processed monitoring data.

S104CB2: Integrate the processed monitoring data in a graphical form to obtain tabular data in tabular form and graphic data in graphical form respectively.

S104CB3: Perform analysis in combination with the table data and the graphic data to obtain the analysis result.

In the application, the data integration of the processed monitoring data can be the integration of the same type of data. For example, the processed monitoring data includes data on the work efficiency of the microservice and a certain type of data processed by the microservice. Based on this, the integration of the processed monitoring data can be understood as the concentration and analysis of all data belonging to the work efficiency of microservices.

In the application, the analysis result obtained by analyzing the table data can be, directly according to each data value in the table data, respectively perform operations (difference operation, square difference operation) with each data value in the previous table data, etc. , to get the operand value. Then, according to the preset multiple numerical ranges and the analysis results corresponding to each numerical range, a target numerical range including the operation value is determined, and then the analysis result of the table data can be obtained. The analysis result obtained by analyzing the image data may be that the graphic data is compared with a plurality of preset graphics, and the target preset graphic with the highest similarity with the graphic data is determined from the preset graphics. Based on this, the analysis results corresponding to the target preset graphics can be determined from the analysis results corresponding to the multiple preset graphics respectively.

In the application, after the analysis results are obtained, the monitoring data of the microservice processing platform can also display tabular data in tabular form and graphic data in graphical form. It is understandable that tabular data can only visually display each data value, and the connection between each data value cannot be clearly expressed. Based on this, displaying graphical data in graphical form at the same time allows users to more easily understand the inherent laws of tabular data according to the graphical data when viewing tabular data, so that users can more comprehensively understand monitoring data.

In the application, the microservice processing platform can also receive control instructions issued by the staff, so that the microservice processing platform can manage the working status of the microservices according to the control instructions. Specifically, the above control instructions include, but are not limited to, instructions for controlling microservices to change execution tasks, and instructions for controlling microservices to stop executing tasks. The working state of the above-mentioned control microservice may be that the control microservice is in a service state, an idle state, and the like. What needs to be added is that when the working state of the microservice changes, it can also save the latest working state of the microservice in the database through the data transmission method of asynchronous threads.

Please refer to FIG. 8. FIG. 8 is a structural block diagram of a microservice data processing apparatus provided by an embodiment of the present application. Each module included in the apparatus for processing microservice data in this embodiment is used to execute each step in the embodiment corresponding to FIG. 1 to FIG. 7 . For details, please refer to FIG. 1 to FIG. 7 and related descriptions in the embodiments corresponding to FIG. 1 to FIG. 7 . For convenience of description, only the parts related to this embodiment are shown. Referring to FIG. 8 , the apparatus 800 for processing microservice data includes: a first obtaining module 810, a generating module 820, a second obtaining module 830, and a processing module 840, wherein:

The first obtaining module 810 is configured to determine a target registration center containing registration information of the microservice, and determine the target registration type of the target registration center.

The generating module 820 is configured to generate, in the microservice registration adaptation engine of the microservice processing platform, a target calling interface adapted to the target open interface of the target registration center according to the target registration type.

The second obtaining module 830 is configured to obtain the microservice data of the microservice according to the target calling interface and the target open interface.

A processing module 840, configured to write the microservice data into the database of the microservice processing platform, and perform centralized processing on the microservice data, where the database contains microservices corresponding to multiple microservices one-to-one data.

In one embodiment, the target registry includes a unified registry of the microservice processing platform and an existing registry of the microservice; the apparatus 800 for processing microservice data further includes:

The third obtaining module is configured to obtain the registration information of the microservice if the microservice does not have a corresponding registration center, and deploy the registration information in the unified registration center.

The first determination module is configured to determine the registration center corresponding to the microservice as the target registration center of the microservice if the microservice already has a corresponding registration center.

In one embodiment, the apparatus 800 for processing microservice data further includes:

The deletion module is configured to delete the registration information deployed by the microservice in the existing corresponding registry if the microservice already has a corresponding registry.

A deployment module, configured to acquire the registration information of the micro-service, and deploy the registration information in the unified registration center again.

The second determination module is used to determine the framework type of the microservice framework used by the microservice.

The first invocation module is used for invoking a toolkit adapted to the framework type through the microservice monitoring engine of the microservice processing platform.

The second invocation module is configured to access the microservice framework of the microservice according to the toolkit when running the microservice, so as to invoke the service component of the microservice.

The third acquiring module is used to acquire the monitoring data of the microservice when it is running.

The analysis module is used for real-time integrated analysis of monitoring data within a preset time period to obtain analysis results.

The storage module is used for storing the analysis result in the database.

In one embodiment, the third acquisition module is further used for:

Store the monitoring data when the microservice is running in the message queue of the microservice;

The monitoring data in the message queue is written into the file system of the microservice processing platform through an asynchronous thread.

In one embodiment, the analysis module is also used to:

Perform data cleaning processing and data format conversion processing on the monitoring data in turn to obtain processed monitoring data;

Data integration is performed on the processed monitoring data in a graphical form to obtain tabular data in tabular form and graphic data in graphical form respectively;

The analysis result is obtained by performing analysis in combination with the tabular data and the graphic data.

It should be understood that, in the structural block diagram of the data processing apparatus shown in FIG. 8 , each unit/module is used to execute each step in the embodiment corresponding to FIG. 1 to FIG. 7 , while for the embodiment corresponding to FIG. 1 to FIG. The steps in the above have been explained in detail in the above-mentioned embodiments. For details, please refer to FIG. 1 to FIG. 7 and the related descriptions in the corresponding embodiments of FIG. 1 to FIG.

FIG. 9 is a structural block diagram of a microservice processing platform provided by another embodiment of the present application. As shown in FIG. 9 , the microservice processing platform 900 of this embodiment includes: a processor 910 , a memory 920 , and a computer program 930 stored in the memory 920 and executable on the processor 910 , such as a program of a data processing method. When the processor 910 executes the computer program 930, the steps in each of the foregoing embodiments of the data processing methods are implemented, for example, S101 to S104 shown in FIG. 1 . Alternatively, when the processor 910 executes the computer program 930, the functions of each module in the embodiment corresponding to FIG. 8 are implemented, for example, the functions of the modules 810 to 840 shown in FIG. 8 . The specifics are as follows:

A microservice processing platform, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor implementing the computer program to achieve:

In one embodiment, the target registry includes a unified registry of the microservice processing platform and an existing registry of the microservice; when the processor executes the computer program, the processor further implements:

If the microservice does not have a corresponding registration center, obtain the registration information of the microservice, and deploy the registration information in the unified registration center;

If the microservice already has a corresponding registry, the registry corresponding to the microservice is determined as the target registry of the microservice.

In one embodiment, when the processor executes the computer program, it further implements:

If the microservice already has a corresponding registry, delete the registration information deployed by the microservice in the existing corresponding registry;

Acquire the registration information of the microservice, and redeploy the registration information in the unified registration center.

Determine the framework type of the microservice framework used by the microservice;

Call the toolkit adapted to the framework type through the microservice monitoring engine of the microservice processing platform;

When running the microservice, access the microservice framework of the microservice according to the toolkit to invoke the service component of the microservice.

Obtain the monitoring data when the microservice is running;

Perform real-time integrated analysis on monitoring data within a preset time period to obtain analysis results;

The analysis results are stored in a database.

A computer-readable storage medium, the computer-readable storage medium stores a computer program, and the computer program is implemented when executed by a processor:

In one embodiment, the target registry includes a unified registry of the microservice processing platform and an existing registry of the microservice; when the computer program is executed by the processor, it also implements:

In one embodiment, the computer program, when executed by the processor, further implements:

Obtain the monitoring data when the microservice is running;

The analysis results are stored in a database.

Exemplarily, the computer program 930 may be divided into one or more units, and the one or more units are stored in the memory 920 and executed by the processor 910 to complete the present application. One or more units may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program 930 in the microservice processing platform 900 .

The microservice processing platform may include, but is not limited to, the processor 910 and the memory 920 . Those skilled in the art can understand that FIG. 9 is only an example of the microservice processing platform 900, and does not constitute a limitation on the microservice processing platform 900, and may include more or less components than the one shown, or combine some components, Or different components, such as the microservice processing platform, may also include input and output devices, network access devices, buses, and the like.

The so-called processor 910 can be a central processing unit, and can also be other general-purpose processors, digital signal processors, application-specific integrated circuits, off-the-shelf programmable gate arrays or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components Wait. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 920 may be an internal storage unit of the microservice processing platform 900 , such as a hard disk or a memory of the microservice processing platform 900 . The memory 920 may also be an external storage device of the microservice processing platform 900 , such as a pluggable hard disk, a smart memory card, a flash memory card, etc., which are equipped on the microservice processing platform 900 . Further, the memory 920 may also include both an internal storage unit of the microservice processing platform 900 and an external storage device.

Realizing all or part of the processes in the methods of the above embodiments can be completed by instructing the relevant hardware through computer-readable instructions. The computer-readable storage medium can be non-volatile or volatile. The computer-readable instructions may be stored in a non-volatile computer-readable storage medium, and when executed, the computer-readable instructions may include the processes of the above-described method embodiments. Wherein, any reference to memory, storage, database or other medium used in the various embodiments provided in this application may include non-volatile and/or volatile memory.

The above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The recorded technical solutions are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the application, and should be included in the application. within the scope of protection.

Claims

A method for processing microservice data, wherein, applied to a microservice processing platform, the method includes:

Determine the target registry that contains the registration information of the microservice, and determine the target registration type of the target registry;

According to the target registration type, in the microservice registration adaptation engine of the microservice processing platform, a target call interface adapted to the target open interface of the target registry is generated;

Acquire the microservice data of the microservice according to the target calling interface and the target open interface;

The microservice data is written into the database of the microservice processing platform, and the microservice data is centrally processed, and the database contains microservice data corresponding to multiple microservices one-to-one.
The method for processing microservice data according to claim 1, wherein the target registry includes a unified registry of the microservice processing platform and an existing registry of the microservice;

Before the determining of the target registry containing the registration information of the microservice, the method further includes:

If the microservice does not have a corresponding registration center, obtain the registration information of the microservice, and deploy the registration information in the unified registration center;

If the microservice already has a corresponding registry, the registry corresponding to the microservice is determined as the target registry of the microservice.
The method for processing microservice data according to claim 2, wherein before said determining the target registry including the registration information of the microservice, it further comprises:

If the microservice already has a corresponding registry, delete the registration information deployed by the microservice in the existing corresponding registry;

Acquire the registration information of the microservice, and redeploy the registration information in the unified registration center.
The method for processing microservice data according to claim 1, wherein after the microservice data is written into the database of the microservice processing platform and the microservice data is centrally processed, the method further comprises: :

Determine the framework type of the microservice framework used by the microservice;

Call the toolkit adapted to the framework type through the microservice monitoring engine of the microservice processing platform;

When running the microservice, access the microservice framework of the microservice according to the toolkit to invoke the service component of the microservice.
The method for processing microservice data according to claim 4, wherein when running the microservice, the microservice framework of the microservice is accessed according to the toolkit, so as to call the service component of the microservice after ,Also includes:

Obtain the monitoring data when the microservice is running;

Perform real-time integrated analysis on monitoring data within a preset time period to obtain analysis results;

The analysis results are stored in a database.
The method for processing microservice data according to claim 5, wherein the obtaining the monitoring data of the microservice runtime comprises:

Store the monitoring data when the microservice is running in the message queue of the microservice;

The monitoring data in the message queue is written into the file system of the microservice processing platform through an asynchronous thread.
The method for processing microservice data according to claim 5, wherein said performing real-time integrated analysis on monitoring data within a preset time period to obtain an analysis result, and obtaining an analysis result, comprising:

Perform data cleaning processing and data format conversion processing on the monitoring data in turn to obtain processed monitoring data;

Data integration is performed on the processed monitoring data in a graphical form to obtain tabular data in tabular form and graphic data in graphical form respectively;

The analysis result is obtained by performing analysis in combination with the tabular data and the graphic data.
An apparatus for processing microservice data, wherein, applied to a microservice processing platform, the apparatus includes:

The first acquisition module is used to determine the target registration center containing the registration information of the microservice, and to determine the target registration type of the target registration center;

A generation module, configured to generate a target call interface adapted to the target open interface of the target registry in the microservice registration adaptation engine of the microservice processing platform according to the target registration type;

A second acquisition module, configured to acquire the microservice data of the microservice according to the target call interface and the target open interface;

A processing module, configured to write the microservice data into the database of the microservice processing platform, and centrally process the microservice data, where the database contains microservice data corresponding to multiple microservices one-to-one .
A microservice processing platform, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor implementing the computer program to achieve:

Determine the target registry that contains the registration information of the microservice, and determine the target registration type of the target registry;

According to the target registration type, in the microservice registration adaptation engine of the microservice processing platform, a target call interface adapted to the target open interface of the target registry is generated;

Acquire the microservice data of the microservice according to the target calling interface and the target open interface;

The microservice data is written into the database of the microservice processing platform, and the microservice data is centrally processed, and the database contains microservice data corresponding to multiple microservices one-to-one.
The microservice processing platform according to claim 9, wherein the target registry includes a unified registry of the microservice processing platform and an existing registry of the microservice; the processor executes the computer program also implements:

If the microservice does not have a corresponding registration center, obtain the registration information of the microservice, and deploy the registration information in the unified registration center;

If the microservice already has a corresponding registry, the registry corresponding to the microservice is determined as the target registry of the microservice.
The microservice processing platform according to claim 10, wherein when the processor executes the computer program, the processor further implements:

If the microservice already has a corresponding registry, delete the registration information deployed by the microservice in the existing corresponding registry;

Acquire the registration information of the microservice, and redeploy the registration information in the unified registration center.
The microservice processing platform according to claim 9, wherein when the processor executes the computer program, the processor further implements:

Determine the framework type of the microservice framework used by the microservice;

Call the toolkit adapted to the framework type through the microservice monitoring engine of the microservice processing platform;

When running the microservice, access the microservice framework of the microservice according to the toolkit to invoke the service component of the microservice.
The microservice processing platform according to claim 12, wherein when the processor executes the computer program, the processor further implements:

Obtain the monitoring data when the microservice is running;

Perform real-time integrated analysis on monitoring data within a preset time period to obtain analysis results;

The analysis results are stored in a database.
The microservice processing platform according to claim 13, wherein when the processor executes the computer program, the processor further implements:

Store the monitoring data when the microservice is running in the message queue of the microservice;

The monitoring data in the message queue is written into the file system of the microservice processing platform through an asynchronous thread.
A computer-readable storage medium storing a computer program, wherein the computer program is executed by a processor to realize:

Determine the target registry that contains the registration information of the microservice, and determine the target registration type of the target registry;

According to the target registration type, in the microservice registration adaptation engine of the microservice processing platform, a target call interface adapted to the target open interface of the target registry is generated;

Acquire the microservice data of the microservice according to the target call interface and the target open interface;

The microservice data is written into the database of the microservice processing platform, and the microservice data is centrally processed, and the database contains microservice data corresponding to multiple microservices one-to-one.
The computer-readable storage medium of claim 15, wherein the target registry includes a unified registry of the microservice processing platform and an existing registry of the microservice; the computer program is executed by the processor also implements:

If the microservice does not have a corresponding registry, obtain the registration information of the microservice, and deploy the registration information in the unified registry;

If the microservice already has a corresponding registry, the registry corresponding to the microservice is determined as the target registry of the microservice.
The computer-readable storage medium of claim 16, wherein the computer program, when executed by the processor, further implements:

If the microservice already has a corresponding registry, delete the registration information deployed by the microservice in the existing corresponding registry;

Acquire the registration information of the microservice, and redeploy the registration information in the unified registration center.
The computer-readable storage medium of claim 15, wherein the computer program, when executed by the processor, further implements:

Determine the framework type of the microservice framework used by the microservice;

Call the toolkit adapted to the framework type through the microservice monitoring engine of the microservice processing platform;

When running the microservice, access the microservice framework of the microservice according to the toolkit to invoke the service component of the microservice.
The computer-readable storage medium of claim 18, wherein the computer program, when executed by the processor, further implements:

Obtain the monitoring data when the microservice is running;

Perform real-time integrated analysis on monitoring data within a preset time period to obtain analysis results;

The analysis results are stored in a database.
The computer-readable storage medium of claim 19, wherein the computer program, when executed by the processor, further implements:

Store the monitoring data when the microservice is running in the message queue of the microservice;

The monitoring data in the message queue is written into the file system of the microservice processing platform through an asynchronous thread.