CN112783910A - Data distribution method and system based on message middleware - Google Patents
Data distribution method and system based on message middleware Download PDFInfo
- Publication number
- CN112783910A CN112783910A CN202110126508.6A CN202110126508A CN112783910A CN 112783910 A CN112783910 A CN 112783910A CN 202110126508 A CN202110126508 A CN 202110126508A CN 112783910 A CN112783910 A CN 112783910A
- Authority
- CN
- China
- Prior art keywords
- data
- message
- middleware
- subscriber
- message middleware
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 49
- 230000008859 change Effects 0.000 claims abstract description 106
- 230000008569 process Effects 0.000 claims description 13
- 230000004075 alteration Effects 0.000 claims 1
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 238000007792 addition Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2308—Concurrency control
- G06F16/2315—Optimistic concurrency control
- G06F16/2322—Optimistic concurrency control using timestamps
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/606—Protecting data by securing the transmission between two devices or processes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Computational Linguistics (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Mathematical Physics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a data distribution method and system based on message middleware, which are used for solving the technical problems that the existing data distribution is not safe enough and the efficiency is not high. The method comprises the following steps: the data distributor determines a data change set and sends the data change set to the message middleware; the message middleware converts the data change set into a change data stream and transmits the change data stream to a data subscriber; and the data subscriber updates the data contained in the received change data stream from the message middleware into a database of the data subscriber. By introducing the message middleware, the data subscriber database is prevented from being updated by directly accessing the data subscriber database by the data distributor, so that the safety is improved; the data is distributed through the message middleware without accessing all data subscribers, so that the instantaneous peak of flow is reduced when the data distribution party distributes the data change set, and the data distribution efficiency is improved.
Description
Technical Field
The present application relates to the field of data exchange technologies, and in particular, to a data distribution method and system based on message middleware.
Background
With the advance of informatization and digitization of enterprises and public institutions, more and more business application systems used by enterprises and public institutions are more and more complex, and interconnection and intercommunication need to be ensured among different business systems or among different business applications in a distributed system, so that data distribution and exchange are conveniently carried out on different business systems or different business applications in the distributed system.
At present, when most of enterprises and public institutions distribute data, data files are transmitted by directly adopting a mode of accessing a database, but the mode of distributing the data is not safe enough and is not efficient.
Disclosure of Invention
The embodiment of the application provides a data distribution method and system based on message middleware, which are used for solving the technical problems of insufficient safety and low efficiency of the existing data distribution.
In one aspect, an embodiment of the present application provides a data distribution method based on message middleware, including: the data distributor determines a data change set and sends the data change set to the message middleware; the message middleware converts the data change set into a change data stream and transmits the change data stream to a data subscriber; and the data subscriber updates the data contained in the received change data stream from the message middleware into a database of the data subscriber.
According to the data distribution method based on the message middleware, firstly, a data distributor organizes and describes data to be distributed by determining a data change set, and determines information of the data and a structural form of the data; then the data change set is sent to a message middleware, the data is distributed to a data subscriber through the message middleware, the safety of the data can be ensured by adopting the message middleware, and the efficiency of data distribution can be improved; and finally, after receiving the data sent by the message middleware, the data subscriber updates the data in the database. The data distribution method and the data distribution system have the advantages that the message middleware is introduced to enable the data distributor to directly access the data subscriber database to update the data subscriber database when the data distributor updates the data subscriber database, so that the safety is improved, the data is distributed through the message middleware, the data distributor only needs to send the data change set to the message middleware, all the data subscribers do not need to be accessed, the instantaneous peak of flow when the data distributor distributes the data change set is reduced, and the efficiency of data distribution is improved.
In one implementation of the present application, before the data distributor sends the data change set to the message middleware, the method further includes: the data distributor judges whether the data change set contains illegal information; in the event that the data changeset is determined to contain illegal information, distribution of the data changeset is terminated.
In one implementation manner of the present application, after the message middleware sends the change data stream to the data subscriber, the method further includes: the message middleware judges whether the distribution of the changed data stream is successful; when the changed data stream is not successfully distributed, a first retry scheme is executed and retransmission is performed.
In an implementation manner of the present application, when the changed data stream is not successfully distributed, executing a first retry scheme to perform retransmission, specifically including: the message middleware resends the changed data stream to the data subscriber until the data change set is successfully distributed; and the message middleware records the retransmission times in the process of retransmitting the changed data stream.
In one implementation manner of the application, the message middleware stops the retransmission process and sends the delivery failure alarm to the data distributor when the number of times of retransmission is greater than or equal to a first preset threshold.
In an implementation manner of the present application, the updating, by a data subscriber, data included in a change data stream received from a message middleware to a database of the data subscriber specifically includes: the data subscriber converts the changed data stream into a data change set; analyzing the data change set, and converting the analyzed data change set into an executable structured query language Script (SQL) script; and executing the SQL script to update the database of the data subscriber.
In one implementation manner of the present application, after the SQL script is executed, the method further includes: the data subscriber judges whether the SQL script is executed successfully; and executing the second retry scheme to perform re-execution under the condition that the SQL script is not successfully executed.
In an implementation manner of the present application, in a case that the SQL script is not successfully executed, the second retry scheme is executed, and the re-execution specifically includes: the data subscriber re-executes the SQL script until the SQL script is successfully executed; and the data subscriber records the times of execution failure in the process of re-executing the SQL script.
In an implementation manner of the present application, the data subscriber stops the re-execution process and issues an update failure warning when the number of execution failures is greater than or equal to a second preset threshold.
On the other hand, an embodiment of the present application further provides a data distribution system based on message middleware, where the system includes: the data distributor is used for determining the data change set and sending the data change set to the message middleware; the message middleware is used for converting the data change set into a change data stream and transmitting the change data stream to the data subscriber; and the data subscriber is used for updating the data contained in the received changed data stream from the message middleware into a database of the data subscriber.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a flowchart of a data distribution method based on message middleware according to an embodiment of the present application;
fig. 2 is a structural diagram of a data distribution system based on message middleware according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, 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 application.
At present, when most enterprises and public institutions distribute data, a data distributor directly adopts a mode of accessing a data subscriber database to transmit data files, so that the data of a data subscriber is modified; in addition, when a data distributor distributes data, a business application system used by an existing enterprise and public institution may need to distribute a plurality of data subscribers at the same time, so that the instantaneous data traffic sent by the data distributor is huge, data congestion is caused, and the data distribution efficiency is affected.
The embodiment of the application provides a data distribution method and system based on message middleware, which are used for solving the technical problems of insufficient safety and low efficiency of the existing data distribution.
The technical solutions proposed in the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Fig. 1 is a flowchart of a data distribution method based on message middleware according to an embodiment of the present application.
As shown in fig. 1, a data distribution method based on message middleware provided in an embodiment of the present application specifically includes the following steps:
In one embodiment of the present application, the data distributor updates the data in the data subscriber database, including adding data in the data subscriber database, deleting data in the data subscriber database, and modifying data in the data subscriber database. Therefore, the data change set determined by the data distributor should include the required updated data and the updating mode of the data; wherein, the updating mode comprises: addition, deletion and modification.
Specifically, the data changeset should contain information of the data distributor, i.e. information of the system or business application to which the data changeset belongs, so as to describe the source of the data; the data changeset should also contain the structure of the data changeset to describe the representation form, or storage form, of the data; it should be noted that, the structure of the data change set includes data tables, fields, and data row range conditions or relationship description information between multiple data tables; the data change set also comprises data subscriber information, namely system or service application information required to be configured by the data change set, so as to describe the destination of the data; the data change set can be configured with information of a plurality of data subscribers, so that the data change set updates databases of a plurality of data subscribers needing the same operation; finally, the data change set should contain the data content information of the required update and the update mode of the data content information, so as to determine the specific data in the data subscriber database which needs to be updated and the update operation which needs to be executed on the specific data. In the embodiment of the present application, the data distributor determines the data changeset by organizing the information that the data changeset should contain.
In addition, the data changeset can also contain the type of data to describe what type of data is updated to the data subscriber data; and the data change set may also contain timestamp information to describe when the data distributor has organized the data change set. It should be noted that the type of the data and the timestamp information may be selectively added to the data change set according to the requirement, and the application is not limited herein. It will be appreciated that other information may be added to the data changeset as desired.
Further, the data distributor sends the data change set to the message middleware after determining the data change set. It will be appreciated that the sending of the data change set to the message middleware is for the purpose of distributing the data change set to the data subscribers via the message middleware.
In an embodiment of the present application, before the data distribution party uploads the data change set to the message middleware, the data subscription party further parses the determined data change set, determines whether the data change set contains illegal information, and terminates the distribution of the data change set by the data subscription party when the data change set contains illegal information.
The illegal information mentioned in the embodiment of the present application is source information, destination information or data information of an error in the data change set, and structural information of the data change set that does not conform to the format of the data change set; in addition, specific sensitive words and sentences can be set as illegal information according to requirements, and when the message middleware determines that the data change set contains the specific sensitive words and sentences, the distribution of the data change set is terminated.
And 102, the message middleware converts the data change set into a change data stream and distributes the change data stream to the data subscriber.
In one embodiment of the present application, after receiving the data change set sent by the data distributor, the message middleware first converts the data change set into a change data stream, and stores the converted change data stream in its message queue. It will be appreciated that since the distribution of data between systems or business applications is actually the delivery of a data stream, the message middleware needs to convert the data changeset into a change data stream.
Further, after the message middleware converts the data change set into a change data stream and stores the change data stream in the message queue thereof, the message middleware calls a preset publishing method therein, and distributes the change data stream stored in the message queue to each data subscriber included in the forwarding information according to the forwarding information included in the change data stream.
Further, after the message middleware distributes the change data stream, an output interface of the message middleware sends a return value; wherein, the return value can judge whether the distribution of the change data stream is successful. For example, in the case that a return value sent by an output interface of the message middleware is 1, it is determined that the distribution of the changed data stream is successful; and determining that the distribution of the change data stream fails when the return value sent by the output interface of the message middleware is 0.
In the case that the distribution of the changed data stream is not successful, the message middleware executes a first retry scheme to resend the changed data stream.
Specifically, when the changed data stream is not successfully distributed, the changed data stream is stored in the message queue again, and then the message middleware calls the preset publishing method again to resend the changed data stream to each data subscriber included in the forwarding information. And when the retransmission of the changed data stream is still not successful in distribution, the data stream is retransmitted circularly until the data change set is distributed to each data subscriber. And when the retransmission is circulated, the message middleware records the retransmission times, stops the retransmission process and sends a distribution failure alarm to the data distributor when the retransmission times are greater than or equal to a first preset threshold value. For example, setting the first preset threshold to be 5, when the message middleware distributes the changed data stream to the data subscriber, if the distribution is unsuccessful, the message middleware will continuously and repeatedly distribute the changed data stream to the data subscriber, and the retransmission will not be stopped until the distribution is successful or the number of times of repeated distribution reaches 5; after the distribution is repeated for 5 times, the message middleware stores the changed data stream with the distribution failure in the message queue again, and sends a warning of the distribution failure to the data distributor to wait for manual intervention processing.
The embodiment of the invention distributes the data stream by introducing the message middleware, so that the data distributor is prevented from directly accessing the data subscriber database to update the data subscriber database, the safety is improved, the data is distributed by the message middleware, the data distributor only needs to send the data change set to the message middleware, all the data subscribers do not need to be accessed, the instantaneous peak of the flow when the data distributor distributes the data change set is reduced, and the efficiency of data distribution is improved.
And step 103, the data subscriber updates the data contained in the received change data stream from the message middleware to a database of the data subscriber.
In one embodiment of the present application, after the message middleware distributes the changed data stream to each data subscriber, each data subscriber first converts the changed data stream into a data change set. Since the system or business application can recognize the format of the data changeset, not the format of the change data stream, the data subscriber needs to convert the change data stream into a data changeset.
Further, after the data subscriber converts the changed data stream into the data change set, the data subscriber parses the data change set, and converts the parsed data change set into an executable SQL script and stores the executable SQL script in a storage medium of the data subscriber. It should be noted that, since addition, deletion, and modification are all specific update operations, the data change set needs to be converted into an executable SQL script. After the conversion is completed, the data subscriber calls the updating module therein to execute the converted SQL script, and after the execution is completed, the updating operation of adding, deleting or modifying the database of the data subscriber can be realized.
When the execution of the SQL script is finished, the updating module of the data subscriber returns a return value which can judge whether the execution is successful. And under the condition that the SQL script is not successfully executed, the data subscriber executes a second retry scheme and re-executes the changed data stream.
Specifically, when the SQL script is not executed successfully, the SQL script is stored in the storage medium of the data subscriber again, and then the update module of the data subscriber executes the SQL script again. And under the condition that the SQL script is not executed successfully again, the SQL script is executed again circularly until the SQL script is executed successfully, and the database of the data subscriber is updated. And when the data subscriber circularly executes again, the data subscriber records the number of times of re-execution, and when the number of times of re-execution is greater than or equal to a first preset threshold, the re-execution process is stopped, and an update failure warning is sent out to wait for the data subscriber to perform manual intervention processing.
Based on the same inventive concept, the embodiment of the present application further provides a data distribution system based on message middleware, and the structure of the data distribution system is shown in fig. 2.
Fig. 2 is a data distribution system based on message middleware according to an embodiment of the present application. As shown in fig. 2, a data distribution system based on message middleware provided in an embodiment of the present application includes: data distributor 201, message middleware 202, data subscriber 203.
Those skilled in the art will appreciate that the message-middleware based data distribution system architecture shown in FIG. 2 does not constitute a limitation of the message-middleware based data distribution system, and in fact, the message-middleware based data distribution system may include more or fewer modules than those shown in FIG. 2, or some modules in combination.
In one embodiment of the application, the data distributor 201 is configured to determine a data change set and send the data change set to the message middleware; the message middleware 202 is used for converting the data change set into a change data stream and transmitting the change data stream to the data subscriber; and the data subscriber 203 is configured to update the data included in the received change data stream from the message middleware to a database of the data subscriber.
The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A method for message-middleware-based data distribution, the method comprising:
the data distributor determines a data change set and sends the data change set to the message middleware;
the message middleware converts the data change set into a change data stream and sends the change data stream to a data subscriber;
and the data subscriber updates the data contained in the received change data stream from the message middleware into a database of the data subscriber.
2. The message-middleware-based data distribution method of claim 1, wherein before the data distributor sends the data change set to the message middleware, the method further comprises:
the data distributor judges whether the data change set contains illegal information;
in the event that the data changeset is determined to contain illegal information, distribution of the data changeset is terminated.
3. The message-middleware-based data distribution method of claim 1, wherein after the message-middleware distributes the changed data stream to a data subscriber, the method further comprises:
the message middleware judges whether the distribution of the change data stream is successful;
and executing a first retry scheme to resend the changed data stream when the changed data stream is not successfully distributed.
4. The message-middleware-based data distribution method according to claim 3, wherein in a case that the distribution of the changed data stream is not successful, a first retry scheme is executed for retransmission, specifically comprising:
the message middleware resends the changed data stream to the data subscriber until the data change set is successfully distributed;
and the message middleware records the retransmission times in the process of retransmitting the changed data stream.
5. The message-middleware-based data distribution method of claim 4,
and the message middleware stops the resending process and sends a distribution failure alarm to the data distributor under the condition that the resending times is greater than or equal to a first preset threshold value.
6. The message-middleware-based data distribution method according to claim 1, wherein the data subscriber updates data included in the received changed data stream from the message middleware to a database of the data subscriber, specifically comprising:
the data subscriber converts the altered data stream into the data alteration set;
analyzing the data change set to convert the data change set into an executable structured query language Script (SQL) script;
and executing the SQL script to update the data contained in the SQL script to the database of the data subscriber.
7. The message-middleware-based data distribution method of claim 6, wherein after executing the SQL script, the method further comprises:
the data subscriber judges whether the SQL script is executed successfully;
and executing a second retry scheme to perform re-execution under the condition that the SQL script is not successfully executed.
8. The message-middleware-based data distribution method of claim 7, wherein, in case that the SQL script is not successfully executed, a second retry scheme is executed for re-execution, specifically comprising:
the data subscriber re-executes the SQL script until the SQL script is successfully executed;
and the data subscriber records the times of execution failure in the process of re-executing the SQL script.
9. The message-middleware-based data distribution method of claim 8,
and the data subscriber stops the re-execution process and sends out an update failure warning under the condition that the execution failure times are greater than or equal to a second preset threshold value.
10. A message-middleware based data distribution system, the system comprising:
the data distributor is used for determining a data change set and sending the data change set to the message middleware;
the message middleware is used for converting the data change set into a change data stream and distributing the change data stream to a data subscriber;
and the data subscriber is used for updating the data contained in the received changed data stream from the message middleware to a database of the data subscriber.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110126508.6A CN112783910A (en) | 2021-01-29 | 2021-01-29 | Data distribution method and system based on message middleware |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110126508.6A CN112783910A (en) | 2021-01-29 | 2021-01-29 | Data distribution method and system based on message middleware |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112783910A true CN112783910A (en) | 2021-05-11 |
Family
ID=75759808
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110126508.6A Pending CN112783910A (en) | 2021-01-29 | 2021-01-29 | Data distribution method and system based on message middleware |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112783910A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107770285A (en) * | 2017-11-13 | 2018-03-06 | 阳光电源股份有限公司 | A kind of distributed caching update method and system |
| CN109451032A (en) * | 2018-11-20 | 2019-03-08 | 上海联寓智能科技有限公司 | A kind of messaging system |
| CN110083660A (en) * | 2019-04-29 | 2019-08-02 | 重庆天蓬网络有限公司 | A kind of method, apparatus of synchrodata, medium and electronic equipment |
| CN110336702A (en) * | 2019-07-11 | 2019-10-15 | 上海金融期货信息技术有限公司 | A kind of system and implementation method of message-oriented middleware |
| CN111026774A (en) * | 2019-12-03 | 2020-04-17 | 深圳前海环融联易信息科技服务有限公司 | Data sequence synchronization method and device, computer equipment and storage medium |
| CN111897878A (en) * | 2020-08-25 | 2020-11-06 | 中国工商银行股份有限公司 | Main and auxiliary data synchronization method and system |
| CN112052227A (en) * | 2020-09-25 | 2020-12-08 | 郑州阿帕斯数云信息科技有限公司 | Data change log processing method and device and electronic equipment |
-
2021
- 2021-01-29 CN CN202110126508.6A patent/CN112783910A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107770285A (en) * | 2017-11-13 | 2018-03-06 | 阳光电源股份有限公司 | A kind of distributed caching update method and system |
| CN109451032A (en) * | 2018-11-20 | 2019-03-08 | 上海联寓智能科技有限公司 | A kind of messaging system |
| CN110083660A (en) * | 2019-04-29 | 2019-08-02 | 重庆天蓬网络有限公司 | A kind of method, apparatus of synchrodata, medium and electronic equipment |
| CN110336702A (en) * | 2019-07-11 | 2019-10-15 | 上海金融期货信息技术有限公司 | A kind of system and implementation method of message-oriented middleware |
| CN111026774A (en) * | 2019-12-03 | 2020-04-17 | 深圳前海环融联易信息科技服务有限公司 | Data sequence synchronization method and device, computer equipment and storage medium |
| CN111897878A (en) * | 2020-08-25 | 2020-11-06 | 中国工商银行股份有限公司 | Main and auxiliary data synchronization method and system |
| CN112052227A (en) * | 2020-09-25 | 2020-12-08 | 郑州阿帕斯数云信息科技有限公司 | Data change log processing method and device and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101037802B1 (en) | Method and system for alert delivery architecture | |
| CN109376160B (en) | Data synchronization method, device, computer equipment and storage medium | |
| CN109451032B (en) | Message transmission system | |
| US20100057515A1 (en) | Dynamic order workflow template instantiator and decoupler | |
| CN102890631A (en) | Method for transmitting message based on persistent message queue and message transmission device | |
| US20110016190A1 (en) | Method and apparatus for realizing message service | |
| CN101075969B (en) | Method, apparatus and system for controlling data transmission | |
| CN110188118B (en) | Data synchronization method and device | |
| CN115080272A (en) | Business data processing method, electronic device and storage medium | |
| CA2603050C (en) | Wireless data device with confirmation and retry capabilities for pushed data | |
| CN103297477B (en) | A kind of data acquisition reporting system and data processing method and proxy server | |
| CN111523897B (en) | Anti-attack method, device and storage medium | |
| CN113590354A (en) | Block chain-based information push method, apparatus, device, medium, and program product | |
| CN112783910A (en) | Data distribution method and system based on message middleware | |
| CN110620819B (en) | Block chain interaction method and device, computer equipment and readable storage medium | |
| EP3026860B1 (en) | Method and system for transmission management of full configuration synchronization between eml-nml | |
| CN112328560A (en) | File scheduling method and system | |
| CN115544034A (en) | Data consistency method and service system | |
| CN101515362A (en) | Method for transmitting data of an overall snapshot of a securities quotation order | |
| US20050076135A1 (en) | UDDI web service registry system based on an ebXML registry and management method therefor | |
| CN116542668A (en) | Block chain-based data processing method, equipment and readable storage medium | |
| CN112860746A (en) | Cache reduction-based method, equipment and system | |
| CN111651284B (en) | Method, device, system and storage medium for processing business data | |
| CN112818020B (en) | Data integration method and device | |
| CN116361016B (en) | Message processing method and system of network controller |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210511 |