CN115495450A

CN115495450A - Data updating method, system and computer storage medium

Info

Publication number: CN115495450A
Application number: CN202211100824.7A
Authority: CN
Inventors: 廖元远; 郭华; 胡昕鑫; 黎坚标; 彭增洪; 贺毅; 左志军
Original assignee: Guangzhou Mino Equipment Co Ltd
Current assignee: Guangzhou Mino Equipment Co Ltd
Priority date: 2022-09-09
Filing date: 2022-09-09
Publication date: 2022-12-20

Abstract

The invention provides a data updating system, a data updating method and a computer readable storage medium. The data update system includes: a first microservice comprising a first database; a second microservice comprising a second database; the first message middleware is used for receiving the update information of the first database in the first micro service and sending the update information of the first database to the second micro service; and the second micro service updates the data of the second database according to the received update information of the first database. The first message middleware transfers the database updating message between the first micro service and the second micro service, so that the data processing amount of the second database is reduced when the second database updates data, and meanwhile, the data division boundary between the databases is clearer.

Description

Data updating method, system and computer storage medium

Technical Field

The invention belongs to the technical field of data processing, and particularly relates to a data updating method, a data updating system and a computer storage medium.

Background

In conventional industrial data management architectures, the functional programs typically share a common stack, while large relational databases are utilized to support the entire platform functional program.

However, in the above data management system, when a slight change occurs in one of the data, the intrinsic overall data may be changed, so that the device management data, especially the periodic data, cannot be updated efficiently and easily. Meanwhile, the whole database is updated in each updating process, so that the method is not beneficial to quick data recovery and historical information tracking.

Disclosure of Invention

In order to overcome the defects of the prior art, the invention provides a data updating method, a system and a computer storage medium, so as to solve the problem of complexity in updating device management data in the prior art.

One embodiment of the present invention provides a data update system, including:

a first microservice comprising a first database;

a second microservice comprising a second database; and

the first message middleware is used for receiving the update information of the first database in the first micro service and sending the update information of the first database to the second micro service; and the second micro service updates the data of the second database according to the received update information of the first database.

In one embodiment, the data update system further comprises:

a third microservice comprising a third database; and

the second message middleware is used for receiving the data updating information of a second database in the second micro service and sending the updating information of the second database to the third micro service; and the third micro service updates the data of the third database according to the received update information of the second database.

In one embodiment, the first micro service comprises one or more of a device ledger basis function module, a standard maintenance flow function module, a fault recovery flow function module and a maintenance activity list function module;

the equipment machine account basic function module, the standard maintenance flow function module, the fault recovery flow function module and the maintenance activity list function module are respectively connected with the first message middleware and send the data updating information of the respective function modules to the first message middleware.

In one embodiment, the first database comprises one or more of a device ledger base database, a standard maintenance flow database, a failure recovery flow database, a maintenance activity list database;

the equipment standing book basic function module is used for processing and updating data of the equipment standing book basic database; the standard maintenance flow function module is used for processing and updating data of the standard maintenance flow database; the fault recovery process function module is used for processing and updating data of the fault recovery process database; the maintenance activity list function module is used for processing and updating data of the maintenance activity list database.

In one embodiment, the first message middleware further comprises a first middleware queue service:

the first middleware queue service is connected with data interfaces corresponding to the equipment ledger basis database, the standard maintenance flow database, the fault recovery flow database and the maintenance activity list database, and is used for respectively storing data update information of the equipment ledger basis database, the standard maintenance flow database, the fault recovery flow database and the maintenance activity list database and generating a maintenance activity rule according to the data update information;

and the first middleware queue service is also connected with a data interface corresponding to the second microservice and used for transmitting the generated maintenance activity rule to the second microservice.

In one embodiment, the second micro-service comprises one or more of a planned work order logic function module, an additional work order logic function module, an equipment short stop logic function module, an equipment failure logic function module and a material management logic function module;

the planning work order logic function module, the additional work order logic function module, the equipment short stop logic function module, the equipment fault logic function module and the material receiving management logic function module are respectively connected with the second message middleware and send the data updating information of the respective function modules to the second message middleware.

In one embodiment, the second database comprises one or more of a planned work order logic database, an additional work order logic database, an equipment short stop logic database, an equipment failure logic database, and a material handling logic database;

the planning work order logic function module is used for processing and updating data of the planning work order logic database; the additional work order logic function module is used for processing and updating data of the additional work order logic database; the equipment short stop logic function module is used for processing and updating data of the equipment short stop logic database; the equipment fault logic function module is used for processing and updating data of the equipment fault logic database; the material receiving management logic function module is used for processing and updating data of the material receiving management logic database.

In one embodiment, the second message middleware further comprises a second middleware queue service:

the second middleware queue service is connected with data interfaces corresponding to the plan work order logic database, the additional work order logic database, the equipment short stop logic database, the equipment fault logic database and the material receiving management logic database, and is used for respectively storing data updating information of the plan work order logic database, the additional work order logic database, the equipment short stop logic database, the equipment fault logic database and the material receiving management logic database and generating a work order pushing message according to the data updating information;

and the second middleware queue service is also connected with a data interface corresponding to the third micro service and used for transmitting the generated work order push message to the third micro service.

In one embodiment, the data of the second database in the second microservice is formed by the data of the first database in the first microservice through business logic calculation.

In one embodiment, the data of the third database in the third micro service is formed by the data of the second database in the second micro service through a result chart generation mode.

In one embodiment, the third micro service comprises one or more of a work order cost statistics display function module, a personnel performance statistics display function module, an equipment KPI statistics display function module and a demand prediction list function module;

and/or the third database comprises one or more of a work order cost statistics display database, a personnel performance statistics display database, an equipment KPI statistics display database and a demand prediction list database; the work order cost statistics display function module is used for processing and updating the data of the work order cost statistics display database; the personnel performance statistics display function module is used for carrying out data processing and updating on the personnel performance statistics display database; the equipment KPI statistics display function module is used for carrying out data processing and updating on the equipment KPI statistics display database; the demand prediction list function module is used for processing and updating data of the demand prediction list database.

An embodiment of the present invention further provides a data updating method, which is used in the data updating system according to any one of the above embodiments, and includes the following steps:

updating a first database in a first microservice;

sending the updated information of the first database to a first message middleware;

and updating a second database in a second micro service according to the updating information of the first database received by the first message middleware.

In one embodiment, the data updating method further includes the following steps:

sending the updated information of the second database to a second message middleware;

and updating a third database in a third microservice according to the updating information of the second database received by the second message middleware.

In one embodiment, the updating process of the second database is as follows:

monitoring a data updating notice of the first message middleware;

according to the data updating notice, the second micro service acquires the updated first data of the first database from the first micro service, and performs service logic calculation on the updated first data of the first database to obtain second data;

and updating the data of the second database according to the second data.

In one embodiment, the update process of the third database is as follows:

monitoring a data updating notice of the second message middleware;

according to the data updating notification, the third micro service acquires the updated second data of the second database from the second micro service, and generates a result chart of the updated second data of the second database to obtain third data;

and updating the data of the third database according to the third data.

One embodiment of the present invention further provides a data updating system, including:

memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the data updating method according to any of the above embodiments.

An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the data updating method according to any one of the above embodiments.

The data updating system provided by the embodiment has the following beneficial effects:

1. setting a first message middleware in a first micro service and a second micro service, wherein the first message middleware is used for receiving data updating information of the first database and sending the data updating information to the second micro service; and the second microserver updates the data of the second database according to the received data updating information of the first database. The first message middleware transfers the database updating message between the first micro service and the second micro service, so that the data processing amount of the second database is reduced when the data is updated, and the data division boundary between the databases is clearer.

2. In one embodiment, a second message middleware is arranged in a second microservice and a third microservice, and the second message middleware is used for receiving data updating information of the second database and sending the data updating information to the third microservice; and the third micro service updates the data of the third database according to the received data updating information of the second database. The updating message is transmitted between the second micro service and the third micro service through the second message middleware, so that the data processing amount of the third database is reduced when the data is updated, and meanwhile, the data division boundary between the databases is clearer.

3. In one embodiment, the first micro service comprises one or more of a device ledger basis function module, a standard maintenance flow function module, a fault recovery flow function module and a maintenance activity list function module; or the second micro service comprises one or more of a planning work order logic function module, an additional work order logic function module, an equipment short stop logic function module, an equipment fault logic function module and a material receiving management logic function module; or the third micro service comprises one or more of a work order cost statistics display function module, a personnel performance statistics display function module, an equipment KPI statistics display function module and a demand prediction list function module. That is, in the first microservice, the second microservice, or the third microservice, in order to facilitate management and classification of data, the first microservice, the second microservice, or the third microservice is divided into a plurality of different types of functional modules according to different types of data to be processed. In this way, when data update is performed, all data in the first microservice, the second microservice or the third microservice does not need to be updated, and only the corresponding microservice needs to be enabled to update part of the data.

4. In one embodiment, the first database comprises one or more of a device ledger base database, a standard maintenance procedures database, a failure recovery procedures database, a maintenance activity list database; the second database comprises one or more of a planned work order logic database, an additional work order logic database, an equipment short stop logic database, an equipment fault logic database and a material receiving management logic database; the third database comprises one or more of a work order cost statistics display database, a personnel performance statistics display database, an equipment KPI statistics display database and a demand prediction list database. That is, for the flexibility and non-redundancy of data, the data in the first database, the second database or the third database are divided into a plurality of sub-databases of different types for storage, when the data is updated, the whole database does not need to be directly updated, and only a new data list needs to be generated at the tail end of the corresponding sub-database, thereby being beneficial to the quick data recovery and the history information tracking.

Drawings

In order to more clearly illustrate the embodiments or technical solutions of the present invention, the drawings used in the embodiments or technical solutions of the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the structures shown in the drawings without creative efforts.

FIG. 1 is a block diagram of a data update system according to an embodiment of the present invention;

FIG. 2 is a block diagram of a first microservice of FIG. 1;

FIG. 3 is a block diagram of the first message middleware of FIG. 1;

FIG. 4 is a schematic diagram of data flow of the first message middleware in FIG. 3 when performing specific tasks;

FIG. 5 is a schematic diagram of data flow of the first message middleware in FIG. 4 when manual equipment ledger basic data import is performed;

FIG. 6 is a block diagram of a second microservice of FIG. 1;

FIG. 7 is a block diagram of second message middleware of FIG. 1;

FIG. 8 is a data flow diagram of the second message middleware of FIG. 7 in performing specific tasks;

FIG. 9 is a schematic diagram illustrating a data flow of the second message middleware in FIG. 8 during statistical display of the equipment maintenance work order;

FIG. 10 is a block diagram of a third microservice of FIG. 1;

FIG. 11 is a flowchart illustrating a data updating method according to an embodiment of the present invention;

FIG. 12 is a detailed flowchart of the update to the second database shown in FIG. 11;

FIG. 13 is a detailed flowchart of the update of the third database shown in FIG. 11;

fig. 14 is a schematic hardware module diagram of a data updating system according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that, if the present invention relates to directional indications (such as up, down, left, right, front, back, 8230; \8230;), the directional indications are only used to explain the relative position relationship between the components, the motion situation, etc. in a specific posture, and if the specific posture is changed, the directional indications are correspondingly changed.

In addition, if there is a description of "first", "second", etc. in an embodiment of the present invention, the description of "first", "second", etc. is for descriptive purposes only and is not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, if the meaning of "and/or" and/or "appears throughout, the meaning includes three parallel schemes, for example," A and/or B "includes scheme A, or scheme B, or a scheme satisfying both schemes A and B. In addition, technical solutions between the embodiments may be combined with each other, but must be based on the realization of the technical solutions by a person skilled in the art, and when the technical solutions are contradictory to each other or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present invention.

Referring to fig. 1, an embodiment of the invention provides a data update system 100. The data update system 100 includes a first microservice 110, a second microservice 120, and first message middleware 140.

The first microservice 110 includes a first database 112.

The second microservice 120 includes a second database 122.

The first message middleware 140 is configured to receive the update information of the first database 112 in the first microservice 110, and send the update information of the first database 112 to the second microservice 120. The second microservice 120 updates the data of the second database 122 according to the received update information of the first database 112.

In this embodiment, the first microservice 110 updates the data of the first database 112 with the device data or the user data obtained from the metadata repository 10. Specifically, the metadata in the metadata base 10 includes manually imported device standing book data and device state data collected by the internet of things collector. For example, when the user manually inputs the device ledger data into the metadata base 10, the first microserver 110 detects the data change of the metadata base 10, and then obtains the updated data from the metadata base 10 to update the data of the first database 112. For another example, the internet of things collector collects the operation state data of the device at preset intervals, the first microserver 110 detects the data change of the metadata base 10, and then obtains the updated data from the metadata base 10 to update the data of the first database 112.

In the data updating system 100 provided in the above embodiment, the first message middleware 140 is disposed in the first microservice 110 and the second microservice 120, and the first message middleware 140 is configured to receive the data updating information of the first database 112 and send the data updating information to the second microservice 120. The second microservice 120 updates the data of the second database 122 according to the received data update information of the first database 112. The database update message is passed between the first microservice 110 and the second microservice 120 through the first message middleware 140, so that the data processing amount of the second database 122 in updating data is reduced, and the data division boundary between the databases is clearer.

Referring also to FIG. 2, in one embodiment, the first microservice 110 includes one or more of a device ledger basis function 1111, a standard maintenance flow function 1112, a failover flow function 1113, and a maintenance activity list function 1114.

The equipment ledger basic function module 1111, the standard maintenance flow function module 1112, the fault recovery flow function module 1113, and the maintenance activity list function module 1114 are respectively connected to the first message middleware 140, and send data update information of each function module to the first message middleware 140.

In this embodiment, in order to facilitate management and classification of data, the first microservice 110 divides a plurality of different types of microservices, such as a device ledger basic function module 1111, a standard maintenance flow function module 1112, a failure recovery flow function module 1113, a maintenance activity list function module 1114, and the like according to different types of data to be processed. In this way, when data in the first microservice 110 is updated by using the metadata in the metadata base 10, all data in the first microservice 110 does not need to be updated, and only the corresponding microservice needs to be enabled to update part of the data, thereby simplifying the data updating process.

In one embodiment, the first database 112 includes one or more of a device ledger basis database 1121, a standard maintenance procedures database 1122, a failure recovery procedures database 1123, and a maintenance activity list database 1124. The device standing book basis function module 1111 is configured to perform data processing and updating on the device standing book basis database 1121. The standard maintenance procedure function module 1112 is configured to perform data processing and updating on the standard maintenance procedure database 1122. The failure recovery flow function module 1113 is configured to perform data processing and updating on the failure recovery flow database 1123. The maintenance activity list function 1114 is used to perform data processing and updating on the maintenance activity list database 1124. That is, for the sake of data flexibility and non-redundancy, the data in the first database 112 is divided into several different types of sub-databases, such as the equipment ledger base database 1121, the standard maintenance flow database 1122, the failure recovery flow database 1123, and the maintenance activity list database 1124, for storage, and when updating data, only a new data list needs to be generated at the end of the corresponding sub-database instead of directly updating the entire database, thereby facilitating the fast data recovery and the tracking of history information. For example, when a user adds a new device, the device ledger data in the metadata base 10 changes. However, when the first microservice 110 updates the data in the first database 112, only the data in the equipment ledger basic database 1121 needs to be updated in the standard maintenance flow database 1122, the fault recovery flow database 1123, and the maintenance activity list database 1124, so as to effectively reduce the computation load of data update.

Referring also to fig. 3, in one embodiment, the first message middleware 140 includes a first data interface 141, a second data interface 142, a third data interface 143, a fourth data interface 144, and a fifth data interface 145. The first data interface 141 is connected to the equipment ledger basis function module 1111, and is configured to receive data update information of the equipment ledger basis database 1121. The second data interface 142 is connected to the standard maintenance procedure function module 1112, and is configured to receive data update information of the standard maintenance procedure database 1122. The third data interface 143 is connected to the failure recovery process function module 1113, and is configured to receive data update information of the failure recovery process database 1123. The fourth data interface 144 is coupled to the maintain active list function 1114 to receive data update information from the maintain active list database 1124. The fifth data interface 145 is connected to the second microservice 120, and is configured to transmit information obtained by processing the data update information of the equipment ledger basic database 1111, the standard maintenance process database 1112, the failure recovery process database 1113, and the maintenance activity list database 1114 to the second microservice 120.

In this embodiment, through the arrangement of the first to fourth data interfaces 141 to 144, the first message middleware 140 can independently receive the data update information of the equipment ledger base database 1121, the standard maintenance flow database 1122, the fault recovery flow database 1123, and the maintenance activity list database 1124, respectively, so as to avoid interference between the update information of different types of databases in the first microservice 110. Meanwhile, through the setting of the fifth data interface 145, the second microservice 120 can listen to and process the data update information in the first microservice 110 at any time.

Referring to fig. 4 and 5, in one embodiment, the first message middleware 140 further includes a first middleware queue service 146.

The first middleware queue service 146 is connected to the data interfaces corresponding to the standard maintenance procedure database 1122, the failure recovery procedure database 1123, and the maintenance activity list database 1124. Specifically, the first middleware queue service 146 is connected to the first to fourth data interfaces 141 to 144, and is configured to store data update information of the equipment ledger base database 1121, the standard maintenance flow database 1122, the failure recovery flow database 1123, and the maintenance activity list database 1124, respectively, and generate a maintenance activity rule according to the data update information.

The first middleware queue service 146 is further coupled to a data interface of the second microservice 120 for communicating the generated maintenance activity rules to the second microservice 120. In particular, the first middleware queue service 146 is further connected to the fifth data interface 145 for transmitting the generated maintenance activity rule to the second microservice 120.

During the process of executing a specific work task (in this embodiment, manual equipment ledger basic data import), the first message middleware 140 obtains a data update message (i.e., an equipment ledger welding shop EXCEL form) from the equipment ledger basic function module 1111 through the message interface API. The message interface API communicates with the equipment ledger basis function module 111 through a middleware network protocol. According to the acquired data update message, the first message middleware 140 stores the data update message (ledger list) in the first middleware queue service 146, and broadcasts the data update message to the outside through the middleware broadcast service. When the planned work order logic function module 121 monitors the data update information transmitted by the middleware broadcast service, the planned work order logic function module 121 extracts the information (maintenance activity generation rule) after the data update information is processed from the middleware queue service, and updates the data in the planned work order logic database 1221 according to the data in the equipment ledger base database 1121. Wherein the middleware broadcast service also communicates with the planning work order logic function module 121 via a middleware network protocol.

In this embodiment, the data of the second database 122 in the second microservice 120 is formed by the data of the first database 112 in the first microservice 110 through business logic calculation. For example, based on the equipment account data in the equipment account base database 1121, such as equipment brand, equipment type, equipment size, equipment procurement date, and the like, the equipment maintenance activity rules, such as maintenance period, maintenance standard, operation steps of maintenance, and the like, can be calculated through business logic.

In one embodiment, the data update system 100 further includes a third microservice 130 and a second messaging middleware 150.

The third microservice 130 includes a third database 132.

The second message middleware 150 is configured to receive the data update information of the second database 122 in the second microservice 120, and send the update information of the second database 122 to the third microservice 130. The third microservice 130 updates the data of the third database 132 according to the received update information of the second database 122.

In the data update system 100 provided in the above embodiment, the second message middleware 150 is provided in the second microservice 120 and the third microservice 130. The second message middleware 150 is configured to receive the data update information of the second database 122, and send the data update information to the third microservice 130. The third microservice 130 updates the data of the third database 132 according to the received data update information of the second database 122. The update message is passed between the second microservice 120 and the third microservice 130 through the second message middleware 150, so that the data processing amount of the third database 132 is reduced when the data is updated, and the data division boundary between the databases is clearer.

Referring also to FIG. 6, in one embodiment, the second microservice 120 includes one or more of a planned work order logic function 1211, an extra work order logic function 1212, an equipment outage logic function 1213, an equipment failure logic function 1214, and a material handling logic function 1215.

The planned work order logic function module 1211, the additional work order logic function module 1212, the equipment short stop logic function module 1213, the equipment failure logic function module 1214 and the material management logic function module 1215 are respectively connected to the second message middleware 150, and send data update information of the respective function modules to the second message middleware 150.

Similarly, in the embodiment, in order to facilitate management and classification of data, the second microservice 120 is divided into a plurality of different types of microservices, such as a planning work order logic function 1211, an additional work order logic function 1212, an equipment short stop logic function 1213, an equipment failure logic function 1214, a material management logic function 1215, and so on, according to different types of data to be processed. In this way, when the data in the second microservice 120 is updated by using the data in the first database 112 in the first microservice 110, all the data in the second microservice 120 does not need to be updated, and only the corresponding microservice needs to be enabled to update part of the data, thereby simplifying the data updating process.

In one embodiment, the second database 122 includes one or more of a planned work order logic database 1221, an extra work order logic database 1222, an equipment outage logic database 1223, an equipment failure logic database 1224, and a collar management logic database 1225.

The planning work order logic function 1211 is configured to perform data processing and updating on the planning work order logic database 1221. The additional work order logic function module 1212 is configured to perform data processing and updating on the additional work order logic database 1222. The device short stop logic function module 1213 is configured to perform data processing and updating on the device short stop logic database 1223. The device failure logic function module 1214 is used to perform data processing and updating on the device failure logic database 1224. The collar management logic function module 1215 is used for data processing and updating of the collar management logic database 1225.

Similarly, for the sake of data flexibility and non-redundancy, the data in the second database 122 is divided into several different types of sub-databases, such as the planned work order logic database 1221, the additional work order logic database 1222, the equipment short stop logic database 1223, the equipment failure logic database 1224, the management logic database 1225, etc. to store, when updating data, only a new data list is generated at the end of the corresponding sub-database without directly updating the whole database, thereby facilitating the fast data recovery and the history information tracking.

Referring also to fig. 7, in one embodiment, the second message middleware 150 includes a sixth data interface 151, a seventh data interface 152, an eighth data interface 153, a ninth data interface 154, a tenth data interface 155, and an eleventh data interface 156.

The sixth data interface 151 is connected to the planned work order logic function module 1211 and configured to receive data update information of the planned work order logic database 1221. The seventh data interface 152 is connected to the additional work order logic function module 1212, and is configured to receive data update information of the additional work order logic database 1222. The eighth data interface 153 is connected to the device short stop logic function module 1213, and is configured to receive data update information of the device short stop logic database 1223. The ninth data interface 154 is connected to the equipment failure logic function module 1214 for receiving data update information of the equipment failure logic database 1224. The tenth data interface 155 is connected to the collar management logic function module 1215 for receiving data update information of the collar management logic database 1225. The eleventh data interface 156 is connected to the third microserver 130, and is configured to transmit the processed data update information of the planned work order logic database 1221, the additional work order logic database 1222, the equipment short stop logic database 1223, the equipment failure logic database 1224, and the material management logic database 1225 to the third microserver 130.

In this embodiment, through the configuration of the sixth to tenth data interfaces 151 to 155, the second message middleware 150 can independently receive the data update information of the planned work order logic database 1221, the additional work order logic database 1222, the equipment short stop logic database 1223, the equipment failure logic database 1224, and the material management logic database 1225, respectively, so as to avoid interference between the update information of different types of databases in the second microservice 120. Meanwhile, through the setting of the eleventh data interface 156, the third microservice 130 can listen and process the data update information in the second microservice 120 at any time.

Referring to fig. 8-9 together, in one embodiment, the second message middleware 150 further includes a second middleware queue service 157.

The second middleware queue service 157 interfaces with data corresponding to the planned work order logic database 1221, the additional work order logic database 1222, the equipment short stop logic database 1223, the equipment failure logic database 1224, and the material management logic database 1225. Specifically, the second middleware queue service 157 is connected to the fifth to tenth data interfaces 151 to 155, and is configured to store data update information of the planned work order logic database 1221, the additional work order logic database 1222, the equipment short stop logic database 1223, the equipment failure logic database 1224, and the material taking management logic database 1225, respectively, and generate a work order push message according to the data update information.

The second middleware queue service 157 is further connected to a data interface corresponding to the third microservice 130, and is configured to transmit the generated work order push message to the third microservice 130. Specifically, the second middleware queue service 157 is further connected to the eleventh data interface 156, and is configured to transmit the generated work order push message to the third microservice 130.

During execution of a specific work task (in this embodiment, device maintenance work order update), the second message middleware 150 obtains a data update message (device maintenance work order list) from the plan work order logic function module 1211 through the message interface API. Wherein the message interface API communicates with the plan work order logic function 1211 via a middleware network protocol. According to the acquired data update message, the second message middleware 150 stores the data update message (work order list) in the second middleware queue service 157, and broadcasts the data update message to the outside through the middleware broadcast service. When the work order cost display statistics microserver 1311 monitors the data update information transmitted by the middleware broadcast service, the work order cost display statistics microserver 1311 takes the information (work order push message) after processing the data update information from the second middleware queue service 157, and updates the data in the work order cost display statistics database 1321 according to the data in the planned work order logic database 1221. The middleware broadcast service also communicates with the work order cost exposure statistics microservice 1311 via a middleware network protocol.

Referring also to FIG. 10, in one embodiment, the third microservice 131 includes one or more of a work order cost statistics presentation function 1311, a personnel performance statistics presentation function 1312, an equipment KPI statistics presentation function 1313, and a demand forecast listing function 1314.

The third database 132 includes one or more of a work order cost statistics presentation database 1321, a personnel performance statistics presentation database 1322, a plant KPI statistics presentation database 1323, and a demand forecast list database 1324. The work order cost statistics display function module 1311 is configured to perform data processing and updating on the work order cost statistics display database 1321. The personnel performance statistics presentation function module 1312 is configured to perform data processing and updating on the personnel performance statistics presentation database 1322. The device KPI statistics display function module 1313 is configured to perform data processing and updating on the device KPI statistics display database 1323. The demand forecast list function 1314 is configured to perform data processing and updating on the demand forecast list database 1324.

In this embodiment, in order to facilitate management and classification of data, the third microservice 131 is divided into multiple different types of microservices, such as a work order cost statistics display function module 1311, a personnel performance statistics display function module 1312, an equipment KPI statistics display function module 1313, and a demand prediction list function module 1314, according to different types of data to be processed. In this way, when the data in the third microservice 130 is updated by using the data in the second database 122 in the second microservice 120, all the data in the third microservice 130 does not need to be updated, but only the corresponding microservice needs to be enabled to update part of the data, thereby simplifying the data updating process. For the flexibility and non-redundancy of data, the data in the third database 132 is divided into a plurality of different types of sub-databases such as a worksheet cost statistics display database 1321, a personnel performance statistics display database 1322, an equipment KPI statistics display database 1323, a demand prediction list database 1324 and the like for storage, when the data is updated, the whole database is not required to be directly updated, and only a new data list is generated at the tail end of the corresponding sub-database, so that the data can be quickly restored and the historical information can be tracked.

In one embodiment, the data of the third database 132 of the third microservice 130 is formed by the data of the second database 122 of the second microservice 120 by way of result graph generation. For example, a presentation chart for the planned work order may be generated based on data in the planned work order logic database 1221 in the second microservice 120.

In general, the data update system 100 provided by the above embodiment has high data usability. In the first microservice 110, the second microservice 120 and the third microservice 130, for the purpose of data flexibility and non-redundancy, data inside each database is divided into a plurality of different types of sub-databases for storage, when data needs to be updated outside each time, the whole database does not need to be updated directly, and only a new data list needs to be generated at the tail end of each sub-database, thereby being beneficial to data quick recovery and historical information tracking.

The data update system 100 provided by the above embodiment has good data aggregation. In the first microservice 110, the second microservice 120 and the third microservice 130, each database only needs to be supported by a specific service, and data with strong relevance is gathered and stored at one place, so that the complexity of the database is greatly reduced, and developers can focus on a specified business function or business requirement in the development process.

The data update system 100 provided by the above embodiment simplifies the data deployment process. In the first microservice 110, the second microservice 120, and the third microservice 130, when data of a certain service is modified, only the data table under the service needs to be adaptively modified, and the data of the full platform does not need to be redeployed.

Specifically, the data update system 100 is formed as follows:

the first microservice 110 obtains metadata from the metadata repository 10. The metadata are manually imported equipment standing book data or equipment state data collected by an internet of things collector.

The metadata is layered to form a first microservice 110. The first microservice 110 is used to provide a storage basis for platform data.

The first microservice 110 is layered to form a second microservice 120. The second microservice 120 is the computing data in the respective database that is strongly related to the data logic.

The business logic data 120 is layered to form a third microservice 130. The third microservice 130 provides application function related processing result data directly to the user.

The division basis of the first microservice 110, the second microservice 120 and the third microservice 130 is based on the concept of "one-to-one library" in microservice architecture, databases in each data layer are mutually related and independently deployed, and data interaction between the data layers is performed through message middleware. When the data is updated, the data is updated through the message middleware through the layer-by-layer progressive relationship.

The operation of the data update system 100 is described below in one specific embodiment:

when the user adds the model a of the front-end robot, the maintenance period T of the front-end robot is updated through the device ledger basic function module 1111 to the maintenance period storage list located in the device ledger basic database 1121, and the updated device ledger basic database 1121 is saved. After the data update of the equipment ledger basic database 1121 is completed, a result of successful data update is returned to the user, and the data update information of the equipment ledger basic database 1121 is sent to the first message middleware 140.

The planned work order logic function module 1211 monitors the notification of the first message middleware 140, extracts a newly added maintenance period data list from the equipment ledger basic database 1121, performs service logic calculation, updates a planned work order pool list in the planned work order logic database 1221, and stores the updated planned work order logic database 1221. After the data in the planned work order logic database 1221 is updated, on one hand, the planned work order logic function 1211 sends a notification to the first message middleware 140 to return a result that the planned work order logic database 1221 is updated successfully; on the other hand, the planning work order logic function module 1211 also transmits the data update information of the planning work order logic database 1221 to the second message middleware 150.

The work order cost statistics display function 1311 monitors the notification of the second message middleware 150, takes out a newly added plan work order data list from the plan work order logic database 1221, generates a result chart display result, and stores the generated result chart display result in the work order cost statistics display database 1321. After the data update of the work order cost statistics display database 1321 is completed, the work order cost statistics display function module 1311 sends a notification to the second message middleware 150, and returns a result of successful execution of the work order cost statistics display function module 1311.

Referring to fig. 11, an embodiment of the present invention provides a data updating method for the data updating system 100 according to any of the above embodiments. The data updating method comprises the following steps:

updating a first database 112 in the first microservice 110;

sending the updated information of the first database 112 to the first message middleware 140;

the second database 122 in the second microservice 120 is updated according to the update information of the first database 112 received by the first message middleware 140.

In the data updating method provided in the above embodiment, a first message middleware 140 is disposed in the first microservice 110 and the second microservice 120, and the first message middleware 140 is configured to receive the data updating information of the first database 112 and send the data updating information to the second microservice 120. The second microservice 120 updates the data of the second database 122 according to the received data update information of the first database 112. The update message is transmitted between the first microservice 110 and the second microservice 120 through the first message middleware 140, so that the data processing amount of the whole database is reduced when the data is updated, and the data division boundary between the databases is clearer.

sending the updated information of the second database 122 to a second message middleware 150;

the third database 132 in the third microservice 130 is updated according to the update information of the second database 122 received by the second message middleware 150.

Referring also to fig. 12, in one embodiment, the second database is updated as follows:

listening for a data update notification of the first message middleware 150;

according to the data update notification, the second microserver 120 obtains the updated first data of the first database 112 from the first microserver 110, and performs service logic calculation on the updated first data of the first database 112 to obtain second data;

and updating the data of the second database 122 according to the second data.

Referring also to fig. 13, in one embodiment, the third database 132 is updated as follows:

listening for a data update notification of the second message middleware 150;

according to the data update notification, the third microserver 130 obtains the updated second data of the second database 122 from the second microserver 120, and generates a result chart of the updated second data of the second database 122 to obtain third data;

the data of the third database 132 is updated according to the third data.

Referring to fig. 14, an embodiment of the present invention provides a data updating system 200, including:

a memory 220, a processor 210 and a computer program 240 stored on the memory 220 and executable on the processor 210, the computer program 240, when executed by the processor 210, implementing the steps of the data updating method according to any one of the above embodiments. In particular, the processor 210, memory 220, and computer program 240 transmit data via a data bus 230.

One embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the data updating method according to any one of the above embodiments.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention, and all modifications and equivalents of the present invention, which are made by the contents of the present specification and the accompanying drawings, or directly/indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A data update system, comprising:

a first microservice comprising a first database;

a second microservice comprising a second database; and

the first message middleware is used for receiving the update information of the first database in the first micro service and sending the update information of the first database to the second micro service; and the second microserver updates the data of the second database according to the received updating information of the first database.

2. The data update system of claim 1, further comprising:

a third microservice comprising a third database; and

3. The data update system of claim 1,

the first micro service comprises one or more of an equipment ledger basic function module, a standard maintenance flow function module, a fault recovery flow function module and a maintenance activity list function module;

the equipment machine account basic function module, the standard maintenance flow function module, the fault recovery flow function module and the maintenance activity list function module are respectively connected with the first message middleware and send data updating information to the first message middleware.

4. The data update system of claim 3,

the first database comprises one or more of an equipment ledger basic database, a standard maintenance flow database, a fault recovery flow database and a maintenance activity list database;

the equipment standing book basic function module is used for processing and updating data of the equipment standing book basic database;

the standard maintenance flow function module is used for processing and updating data of the standard maintenance flow database;

the fault recovery process function module is used for processing and updating data of the fault recovery process database;

the maintenance activity list function module is used for processing and updating data of the maintenance activity list database.

5. The data update system of claim 4, wherein the first message middleware further comprises a first middleware queue service:

the first middleware queue service is respectively connected with data interfaces corresponding to the equipment ledger basis database, the standard maintenance flow database, the fault recovery flow database and the maintenance activity list database, and is used for respectively storing data update information of the equipment ledger basis database, the standard maintenance flow database, the fault recovery flow database and the maintenance activity list database and generating a maintenance activity rule according to the data update information;

the first middleware queue service is also connected with a data interface of the second microservice and used for transmitting the generated maintenance activity rule to the second microservice.

6. The data update system of claim 2,

the second micro service comprises one or more of a planning work order logic function module, an additional work order logic function module, an equipment short stop logic function module, an equipment fault logic function module and a material receiving management logic function module;

the planning work order logic function module, the additional work order logic function module, the equipment short stop logic function module, the equipment fault logic function module and the material receiving management logic function module are respectively connected with the second message middleware and send data updating information of the function modules to the second message middleware.

7. The data update system of claim 6,

the second database comprises one or more of a planned work order logic database, an additional work order logic database, an equipment short stop logic database, an equipment fault logic database and a material receiving management logic database;

the planning work order logic function module is used for processing and updating data of the planning work order logic database;

the additional work order logic function module is used for processing and updating data of the additional work order logic database;

the equipment short stop logic function module is used for processing and updating data of the equipment short stop logic database;

the equipment fault logic function module is used for processing and updating data of the equipment fault logic database;

the material receiving management logic function module is used for processing and updating data of the material receiving management logic database.

8. The data update system of claim 7, wherein the second message middleware further comprises a second middleware queue service:

the second middleware queue service is connected with data interfaces corresponding to the planned work order logic database, the additional work order logic database, the equipment short stop logic database, the equipment fault logic database and the material receiving management logic database, and is used for respectively storing data updating information of the planned work order logic database, the additional work order logic database, the equipment short stop logic database, the equipment fault logic database and the material receiving management logic database and generating a work order push message according to the data updating information;

and the second middleware queue service is also connected with a data interface of the third micro service and used for transmitting the generated work order push message to the third micro service.

9. The data update system of any of claims 2, 6-8,

the third micro service comprises one or more of a work order cost statistics display function module, a personnel performance statistics display function module, an equipment KPI statistics display function module and a demand prediction list function module;

the third database comprises one or more of a work order cost statistics display database, a personnel performance statistics display database, an equipment KPI statistics display database and a demand prediction list database;

the work order cost statistics display function module is used for processing and updating the data of the work order cost statistics display database;

the personnel performance statistics display function module is used for carrying out data processing and updating on the personnel performance statistics display database;

the equipment KPI statistics display function module is used for performing data processing and updating on the equipment KPI statistics display database;

the demand prediction list function module is used for processing and updating data of the demand prediction list database.

10. A data update method for a data update system according to any one of claims 1 to 9, comprising the steps of:

updating a first database in a first microservice;

11. The data updating method of claim 10, further comprising the steps of:

12. The data updating method of claim 10, wherein the updating process of the second database is as follows:

monitoring a first data updating notice of the first message middleware;

according to the first data updating notice, the second micro service acquires the updated first data of the first database from the first micro service, and performs service logic calculation on the updated first data of the first database to obtain second data;

and updating the data of the second database according to the second data.

13. The data updating method of claim 11, wherein the updating process of the third database is as follows:

monitoring a second data update notification of the second message middleware;

according to a second data updating notice, the third micro service acquires updated second data of the second database from the second micro service, and generates a result chart of the updated second data of the second database to obtain third data;

and updating the data of the third database according to the third data.

14. A data update system, comprising:

memory, processor and computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps of the data updating method according to any one of claims 10 to 13.

15. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the data updating method according to any one of the claims 10-13.