CN116303760A - Data synchronization method and device of bank core system and electronic equipment - Google Patents
Data synchronization method and device of bank core system and electronic equipment Download PDFInfo
- Publication number
- CN116303760A CN116303760A CN202211698001.9A CN202211698001A CN116303760A CN 116303760 A CN116303760 A CN 116303760A CN 202211698001 A CN202211698001 A CN 202211698001A CN 116303760 A CN116303760 A CN 116303760A
- Authority
- CN
- China
- Prior art keywords
- data
- request information
- data synchronization
- synchronization request
- core system
- 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 90
- 230000001360 synchronised effect Effects 0.000 claims abstract description 135
- 238000012545 processing Methods 0.000 claims description 31
- 230000008859 change Effects 0.000 abstract description 7
- 238000005516 engineering process Methods 0.000 description 12
- 230000005540 biological transmission Effects 0.000 description 11
- 238000004590 computer program Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 4
- 238000013499 data model Methods 0.000 description 4
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000010076 replication Effects 0.000 description 2
- 230000032683 aging Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000000712 assembly Effects 0.000 description 1
- 238000000429 assembly Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013481 data capture Methods 0.000 description 1
- 238000013075 data extraction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 229940004975 interceptor Drugs 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 230000001902 propagating effect Effects 0.000 description 1
- 230000003068 static 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/275—Synchronous replication
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a data synchronization method, a data synchronization device and electronic equipment of a bank core system, wherein the method comprises the following steps: the method comprises the steps of calling first data synchronization request information in a message middleware, analyzing data of the first data synchronization request information to obtain second data synchronization request information, and enabling the second data synchronization request information to be directly executed by a target bank core system, wherein the first data synchronization request information is information for requesting to synchronize service data to be synchronized to be target service data; and sending the second data synchronization request information to the target bank core system so as to update the business data needing to be synchronized in the database of the target bank core system. The method can effectively reduce the use cost, and can synchronize the change to the target bank core system in real time when the system changes the data, thereby realizing the data synchronization, effectively ensuring the data consistency among the systems, and further solving the problem of poor real-time performance of the data synchronization in each bank core system realized by the prior art.
Description
Technical Field
The present invention relates to the field of data synchronization technologies, and in particular, to a data synchronization method and apparatus for a banking core system, a computer readable storage medium, and an electronic device.
Background
When the data of the bank core system is changed, the change information cannot be synchronized with other systems in time, so that the data of the bank core systems are inconsistent.
The technical architecture evolves from a single application to a distributed architecture, the data storage evolves from a shared storage to a plurality of data storage to coexist, and in order to meet the continuously developed service demands, a set of solution is often constructed by a plurality of systems to meet the different service demands of clients, and the communication among the systems can be realized through RPC, HTTP, message middleware and other modes, and the communication modes shield the differences in the aspects of system architecture, realization language and the like.
In the system, because the data structures are unified, the data storage adopts the same database or the storage systems such as redis and ES, the real-time synchronization of the data can be realized through the self-owned data synchronization technology such as stream replication or multiple copies, the systems often have larger differences in the design of the data structures due to different service emphasis, the self-owned data synchronization technology of the storage system cannot be directly adopted, and the data can be converted into the matched data structure usually by the system for realizing data extraction, analysis and conversion.
Some mature technologies such as DTS and CDC are adopted for data synchronization of heterogeneous systems, and log changes are extracted in real time and transmitted to a target system for analysis by monitoring database logs. The data can be synchronized from one system to another by periodic extraction, conversion, mapping, etc. of timing tasks, which is not highly time-efficient.
The techniques of stream replication, duplication, etc. are the data synchronization techniques of the middleware such as database, redis, ES, etc. and are mature and stable, but the data synchronization among different components cannot be realized, and the method is only suitable for the data synchronization of isomorphic systems.
The DTS technology and the CDC technology can realize the data synchronization of heterogeneous systems, but the technologies are limited by copyright and need to be used in a paid mode, the operation and maintenance aspect needs to be maintained by special personnel of suppliers, the problems need to be communicated with each other with high time cost, and the problem positioning and solving efficiency is low. The timing task synchronization is performed by periodically pulling data, and is only suitable for service scenes with low timeliness requirements.
Disclosure of Invention
The main objective of the present application is to provide a method, an apparatus, a computer readable storage medium and an electronic device for synchronizing data in a banking core system, so as to at least solve the problem of poor real-time performance of data synchronization in each banking core system in the prior art.
To achieve the above object, according to one aspect of the present application, there is provided a data synchronization method of a banking core system, the method including: the method comprises the steps of calling first data synchronization request information in a message middleware, analyzing data of the first data synchronization request information to obtain second data synchronization request information, and enabling the second data synchronization request information to be directly executed by a target bank core system, wherein the first data synchronization request information is information for requesting to synchronize service data to be synchronized to be target service data, the service data to be synchronized is service data different from service data in a source bank core system in the target bank core system, and the target service data is service data corresponding to the service data to be synchronized in the source bank core system; and sending the second data synchronization request information to the target bank core system to update the business data needing synchronization in the database of the target bank core system.
Optionally, the retrieving the first data synchronization request information in the message middleware includes: and calling the first data synchronization request information in the message middleware in real time.
Optionally, after sending the second data synchronization request information to the target banking core system, the method further comprises: determining whether the service data to be synchronized is successfully synchronized into target service data; under the condition that the service data to be synchronized is successfully synchronized into target service data, determining that data synchronization work is completed, wherein the data synchronization work is used for representing the work of updating the service data to be synchronized in a database of a target bank core system; and under the condition that the service data to be synchronized is not successfully synchronized as target service data, storing the first data synchronization request information in the message middleware into a retry queue of the message middleware, and calling the first data synchronization request information of the retry queue, wherein the retry queue is the first data synchronization request information which needs to be retried in the message middleware.
Optionally, retrieving the first data synchronization request information of the retry queue includes: after the second data synchronization request information is sent to the target bank core system, under the condition that a first preset time passes, the first data synchronization request information of the retry queue is called; and recording the retry times of the first data synchronization request information.
Optionally, after recording the number of retries of the first data synchronization request information, the method further includes: and under the condition that the retry time is greater than or equal to the preset time, moving the first data synchronization request information of the retry queue to a dead message queue of the message middleware, wherein the dead message queue is a queue which does not call information any more.
Optionally, after recording the number of retries of the first data synchronization request information, the method further includes: and under the condition that the service data to be synchronized is determined to be synchronized into target service data and a second preset time is passed, the first data synchronization request information in the retry queue is called.
Optionally, the first data synchronization request information and the second data synchronization request information are both sql object serialization information.
According to another aspect of the present application, a data synchronization device of a banking core system is provided, where the device includes a first processing unit and a second processing unit, where the first processing unit is configured to retrieve first data synchronization request information in a message middleware, parse data of the first data synchronization request information to obtain second data synchronization request information, so that the second data synchronization request information may be directly executed by a target banking core system, where the first data synchronization request information is information requesting to synchronize service data to be synchronized as target service data, where the service data to be synchronized is service data in the target banking core system different from service data in a source banking core system, and the target service data is service data corresponding to the service data to be synchronized in the source banking core system; and the second processing unit is used for sending the second data synchronization request information to the target bank core system so as to update the business data which need to be synchronized in the database of the target bank core system.
According to another aspect of the present application, there is provided a computer readable storage medium, where the computer readable storage medium includes a stored program, and when the program runs, the device in which the computer readable storage medium is controlled to execute any one of the data synchronization methods of the banking core system.
According to another aspect of the present application, there is provided an electronic device comprising one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising a data synchronization method for executing any one of the banking core systems.
By the technical scheme, the first data synchronization request information in the message middleware is called, the data of the first data synchronization request information is analyzed to obtain the second data synchronization request information, and then the second data synchronization request information is sent to the target bank core system to update the business data needing to be synchronized in the database of the target bank core system.
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 embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
fig. 1 is a block diagram showing a hardware configuration of a mobile terminal for performing a data synchronization method of a banking core system according to an embodiment of the present application;
FIG. 2 shows a flow chart of a method of data synchronization for a banking core system provided in accordance with an embodiment of the present application;
fig. 3 shows a schematic diagram of a data synchronization device of a banking core system according to an embodiment of the present application.
Wherein the above figures include the following reference numerals:
102. a processor; 104. a memory; 106. a transmission device; 108. and an input/output device.
Detailed Description
It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other. The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate in order to describe the embodiments of the present application described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
For convenience of description, the following will describe some terms or terms related to the embodiments of the present application:
DTS: the data transmission service (Data Transmission Service) provides data migration, data synchronization and data subscription to a unified database data transmission service.
CDC: change data acquisition (Change Data Capture) for capturing submitted changes from the database and propagating the changes to downstream users.
MyBatis: is an excellent persistence layer framework that can use simple XML or annotations to configure and map native information, mapping interfaces and objects to records in a database.
RocketMQ: open source message middleware of pure java, distributed and queue models supports transaction messages, sequence messages, batch messages, timing messages, message backtracking and the like.
Transaction message: it is meant that the application local transaction and the send message operation may be defined into a global transaction, either with success or with failure.
As described in the background art, DTS and CDC technologies can realize data synchronization of heterogeneous systems, but these technologies are limited by copyright and need to be paid for use, and in terms of operation and maintenance, the operation and maintenance need to be maintained by a vendor, and problems need to be communicated with each other with relatively high time cost, and the problem positioning and solving efficiency is not high. The timing task synchronization is performed by periodically pulling data, is only suitable for service scenes with low timeliness requirements, and aims to solve the problem that the real-time performance of data synchronization in each bank core system is poor in the prior art.
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.
The method embodiments provided in the embodiments of the present application may be performed in a mobile terminal, a computer terminal or similar computing device. Taking the mobile terminal as an example, fig. 1 is a block diagram of a hardware structure of a mobile terminal of a data synchronization method of a bank core system according to an embodiment of the present invention. As shown in fig. 1, a mobile terminal may include one or more (only one is shown in fig. 1) processors 102 (the processor 102 may include, but is not limited to, a microprocessor MCU or a processing device such as a programmable logic device FPGA) and a memory 104 for storing data, wherein the mobile terminal may also include a transmission device 106 for communication functions and an input-output device 108. It will be appreciated by those skilled in the art that the structure shown in fig. 1 is merely illustrative and not limiting of the structure of the mobile terminal described above. For example, the mobile terminal may also include more or fewer components than shown in fig. 1, or have a different configuration than shown in fig. 1.
The memory 104 may be used to store a computer program, for example, a software program of application software and a module, such as a computer program corresponding to a display method of device information in an embodiment of the present invention, and the processor 102 executes the computer program stored in the memory 104 to perform various functional applications and data processing, that is, to implement the above-described method. Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located relative to the processor 102, which may be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof. The transmission device 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, simply referred to as NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is configured to communicate with the internet wirelessly.
In this embodiment, a method of synchronizing data of a banking core system operating on a mobile terminal, a computer terminal or similar computing device is provided, it being noted that the steps shown in the flowchart of the figures may be performed in a computer system such as a set of computer executable instructions, and that although a logical sequence is shown in the flowchart, in some cases the steps shown or described may be performed in a different order than that shown.
Fig. 2 is a flowchart of a data synchronization method of a banking core system according to an embodiment of the present application. The method is applied to the MyBatis framework, as shown in FIG. 2, and comprises the following steps:
step S201, first data synchronization request information in a message middleware is called, data of the first data synchronization request information is analyzed to obtain second data synchronization request information, so that the second data synchronization request information can be directly executed by a target bank core system, wherein the first data synchronization request information is information for requesting to synchronize service data to be synchronized as target service data, the service data to be synchronized is service data different from service data in a source bank core system in the target bank core system, and the target service data is service data corresponding to the service data to be synchronized in the source bank core system;
Specifically, the first data synchronization request information is a transaction message, the message middleware is a RocketMQ, and in order to ensure the consistency of database operation and MQ messages, the transaction message of the RocketMQ needs to be used so as not to cause the situation that the database operation is successful but the MQ writing fails. The source banking core system executes local logic, intercepting insert, update, delete type SQL against the database by the interceptor of MyBatis plug-in. The source banking core system sends the intercepted SQL to the RocketMQ specified topic (half message) in the type of transaction message. The source bank core system realizes an Interceptor of MyBatis framework, intercepts the database insert, update, delete type SQL generated by the operation of the business system, and sends the SQL to the designated topic of the RocketMQ. The RocketMQ server responds to the message writing result, and if the writing fails, the half message is invisible to the target system, and the producer local logic rolls back. If the RocketMQ server responds to the successful writing of the message, the local logic is continuously executed, the Commit or the Rollback of the RocketMQ is executed according to the local transaction state (the Commit operation generates a message index, the message is visible to consumers), if the situation that the half message is not Commit or not Rollback is generated in the process, the RocketMQ server actively initiates a 'check', checks the state of the local transaction corresponding to the check message, and re-Commit or Rollback is carried out according to the local transaction state. The target bank core system pulls the message from the appointed topic and analyzes the SQL in the message body, but the SQL in the message body cannot be directly replayed to complete data writing due to the difference of the data model of the source bank core system and the target bank core system. Providing a data object matched with the target system data model, wherein the data object comprises a target system model name, an SQL operation type and the like; the corresponding relation between the data model of the source system and the data model of the target system is set in advance in the form of a configuration file, and service starting is carried out and is loaded into a memory; and pulling the message from the designated topic, analyzing the corresponding model name and field data in the SQL, finding the model name and the data transmission object corresponding to the target system by combining the model name and the cached model mapping relation, and deserializing the SQL parameter information into the data object of the target system. In order to realize the automatic processing of the whole flow, the SQL sentence is dynamically assembled by analyzing the acquired target system data object through the message in the link, the state object of MyBatis is generated and executed, and the data writing is completed.
Step S202, the second data synchronization request information is sent to the target bank core system to update the service data to be synchronized in the database of the target bank core system.
In the above steps, the first data synchronization request information in the message middleware is called, the data of the first data synchronization request information is analyzed to obtain the second data synchronization request information, and then the second data synchronization request information is sent to the target bank core system to update the service data to be synchronized in the database of the target bank core system, so that the service data can be realized based on the open source component without paying, the use cost can be effectively reduced, when the system changes data, the change can be synchronized to the target bank core system in real time, the data synchronization is realized, the data consistency among the systems is effectively ensured, and the problem that the real-time performance of the data synchronization in each bank core system is poor in the prior art is solved.
In one embodiment of the present application, retrieving first data synchronization request information in a message middleware includes: and calling the first data synchronization request information in the message middleware in real time. The real-time performance of the method and the device is guaranteed.
In one embodiment of the present application, after the sending of the second data synchronization request information to the target banking core system, the method further includes: determining whether the service data to be synchronized is successfully synchronized into target service data; under the condition that the service data to be synchronized is successfully synchronized into target service data, determining that data synchronization work is completed, wherein the data synchronization work is used for representing the work of updating the service data to be synchronized in a database of a target bank core system; and under the condition that the service data to be synchronized is not successfully synchronized as target service data, storing the first data synchronization request information in the message middleware into a retry queue of the message middleware, and calling the first data synchronization request information of the retry queue, wherein the retry queue is the first data synchronization request information which needs to be retried in the message middleware.
Specifically, under the condition that the service data to be synchronized is determined to be unsuccessfully synchronized as the target service data, the first data synchronization request information is put into a retry queue so as to facilitate the execution of subsequent re-invoking attempts, and under the condition that the service data to be synchronized is determined to be successfully synchronized as the target service data, the message middleware is informed that the first data synchronization request information is successfully executed, and the first data synchronization request information is not invoked in the follow-up process.
In one embodiment of the present application, the retrieving the first data synchronization request information of the retry queue includes: after the second data synchronization request information is sent to the target bank core system, the first data synchronization request information of the retry queue is called when a first preset time elapses; and recording the retry times of the first data synchronization request information.
Specifically, after the second data synchronization request information is sent to the target bank core system, under the condition that a first preset time passes, the first data synchronization request information of the retry queue is called, and the retry times of the first data synchronization request information are recorded, so that the subsequent first data synchronization request information which cannot be successfully executed is ensured to be placed in a dead message queue in time.
In an embodiment of the present application, after recording the number of retries of the first data synchronization request information, the method further includes: and if the retry number is greater than or equal to a predetermined number, moving the first data synchronization request information of the retry queue to a dead message queue of the message middleware, wherein the dead message queue is a queue which does not call information any more.
Specifically, when the retry number is greater than or equal to the predetermined number, the first data synchronization request information of the retry queue is moved to the dead mail queue of the message middleware, so that the first data synchronization request information which cannot be successfully executed is placed in a place where the first data synchronization request information does not need to be called again, and subsequent meaningless repeated calling attempts are prevented.
In an embodiment of the present application, after recording the number of retries of the first data synchronization request information, the method further includes: and under the condition that the service data to be synchronized is determined to be synchronized into target service data and a second preset time is passed, the first data synchronization request information in the retry queue is called.
Specifically, for example, after determining that the service data to be synchronized is synchronized to the target service data, and after 10s elapsed since that, the first data synchronization request information in the retry queue is called to retry the first data synchronization request information again.
In an embodiment of the present application, the first data synchronization request information and the second data synchronization request information are both sql object serialization information.
The data conversion and synchronization between heterogeneous systems can be realized by adopting an off-line mode, a real-time mode and the like, and the off-line mode generally depends on big data components such as Hadoop, hive, spark and the like, so that the method is suitable for the situations of processing large data volume and having lower aging requirements; the real-time mode generally depends on a stream batch processing framework such as Spark, flink and the like, and is suitable for the situation with high timeliness requirements. However, both the two modes need to build clusters of dependent assemblies, and the resource requirements are more; the method is lighter and can ensure high-aging synchronization.
The data change generated by the system is synchronized to the target system through the quasi-real-time synchronization technology, the target system data is updated in a near real-time mode, the accuracy of system data query is effectively solved, the complexity of system data query is reduced, and the user query experience is improved.
Through the embodiment, the dependency on cluster resources is small, the deployment scale can be determined according to the actual data magnitude, the deployment scale can be quickly stretched, the actual landing is more convenient, transaction information is adopted in data production, a retry mechanism is arranged in data consumption, the final consistency of the data is ensured, the dependency between heterogeneous systems is reduced through decoupling of a source bank core system and a target bank core system by middleware, and the quasi-real-time synchronization efficiency can be achieved.
In order to enable those skilled in the art to more clearly understand the technical solutions of the present application, the implementation process of the data synchronization method of the banking core system of the present application will be described in detail below with reference to specific embodiments.
The embodiment relates to a data synchronization method of a specific bank core system, which comprises the following steps:
step S1: the method comprises the steps of calling first data synchronization request information in a message middleware, analyzing data of the first data synchronization request information to obtain second data synchronization request information, and enabling the second data synchronization request information to be directly executed by a target bank core system, wherein the first data synchronization request information is information for requesting to synchronize service data to be synchronized to be target service data, the service data to be synchronized is service data different from service data in a source bank core system in the target bank core system, and the target service data is service data corresponding to the service data to be synchronized in the source bank core system;
step S2: transmitting the second data synchronization request information to the target bank core system to update the service data to be synchronized in the database of the target bank core system;
Step S3: determining whether the service data to be synchronized is successfully synchronized into target service data; under the condition that the service data to be synchronized is successfully synchronized into target service data, determining that data synchronization work is completed, wherein the data synchronization work is used for representing the work of updating the service data to be synchronized in a database of a target bank core system; storing the first data synchronization request information in the message middleware into a retry queue of the message middleware and calling the first data synchronization request information of the retry queue, wherein the retry queue is the first data synchronization request information which needs to be retried in the message middleware, under the condition that the service data to be synchronized is determined to be unsuccessfully synchronized as target service data;
step S4: after the second data synchronization request information is sent to the target bank core system, the first data synchronization request information of the retry queue is called when a first preset time elapses; recording the retry times of the first data synchronization request information;
step S5: and if the retry number is greater than or equal to a predetermined number, moving the first data synchronization request information of the retry queue to a dead message queue of the message middleware, wherein the dead message queue is a queue which does not call information any more.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer executable instructions, and that although a logical order is illustrated in the flowcharts, in some cases the steps illustrated or described may be performed in an order other than that illustrated herein.
The embodiment of the application also provides a data synchronization device of the bank core system, and it should be noted that the data synchronization device of the bank core system of the embodiment of the application can be used for executing the data synchronization method for the bank core system provided by the embodiment of the application. The device is used for realizing the above embodiments and preferred embodiments, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
The following describes a data synchronization device of a banking core system provided in an embodiment of the present application.
Fig. 3 is a schematic diagram of a data synchronization device of a banking core system according to an embodiment of the present application. As shown in fig. 3, the device includes a first processing unit 31 and a second processing unit 32, where the first processing unit 31 is configured to retrieve first data synchronization request information in a message middleware, parse data of the first data synchronization request information to obtain second data synchronization request information, so that the second data synchronization request information may be directly executed by a target bank core system, where the first data synchronization request information is information for requesting to synchronize service data to be synchronized as target service data, where the service data to be synchronized is service data in the target bank core system that is different from service data in a source bank core system, and the target service data is service data corresponding to the service data to be synchronized in the source bank core system; the second processing unit 32 is configured to send the second data synchronization request information to the target banking core system, so as to update the service data that needs to be synchronized in the database of the target banking core system.
In the device, the first data synchronization request information in the message middleware is fetched, the data of the first data synchronization request information is analyzed to obtain the second data synchronization request information, and then the second data synchronization request information is sent to the target bank core system to update the service data needing to be synchronized in the database of the target bank core system.
In an embodiment of the present application, the first processing unit includes a retrieving module, where the retrieving module is configured to retrieve, in real time, the first data synchronization request information in the message middleware.
In an embodiment of the present application, the apparatus further includes a first determining unit, a second determining unit, and a third determining unit, where after the second data synchronization request information is sent to the target banking core system, the first determining unit is configured to determine whether the service data to be synchronized has been successfully synchronized to the target service data; the second determining unit is used for determining that the data synchronization work is completed under the condition that the to-be-synchronized service data is successfully synchronized into the target service data, wherein the data synchronization work is used for representing the work of updating the service data needing to be synchronized in the database of the target bank core system; and the third determining unit is used for storing the first data synchronization request information in the message middleware into a retry queue of the message middleware and calling the first data synchronization request information in the retry queue when the service data to be synchronized is determined to be unsuccessfully synchronized as target service data, wherein the retry queue is the first data synchronization request information which needs to be retried in the message middleware.
In an embodiment of the present application, the third determining unit includes a first processing module and a second processing module, where the first processing module is configured to, after sending the second data synchronization request information to the target banking core system, invoke the first data synchronization request information of the retry queue when a first predetermined time elapses; the second processing module is used for recording the retry times of the first data synchronization request information.
In an embodiment of the present application, the third determining unit further includes a third processing module, after recording the number of retries of the first data synchronization request information, the third processing module is configured to move the first data synchronization request information of the retry queue to a dead message queue of the message middleware, where the dead message queue is a queue that does not call information any more, if the number of retries is greater than or equal to a predetermined number.
In an embodiment of the present application, the third determining unit further includes a fourth processing module, after recording the retry number of the first data synchronization request information, the fourth processing module is configured to invoke the first data synchronization request information in the retry queue when determining that the service data to be synchronized is the target service data and a second predetermined time elapses.
In an embodiment of the present application, the first data synchronization request information and the second data synchronization request information are both sql object serialization information.
The data synchronization device of the bank core system comprises a processor and a memory, wherein the first processing unit, the second processing unit and the like are stored in the memory as program units, and the processor executes the program units stored in the memory to realize corresponding functions. The modules are all located in the same processor; alternatively, the above modules may be located in different processors in any combination.
The processor includes a kernel, and the kernel fetches the corresponding program unit from the memory. The kernel can be provided with one or more than one kernel, and the problem of poor real-time performance of realizing data synchronization in each bank core system in the prior art is solved by adjusting kernel parameters.
The memory may include volatile memory, random Access Memory (RAM), and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM), among other forms in computer readable media, the memory including at least one memory chip.
The embodiment of the invention provides a computer readable storage medium, which comprises a stored program, wherein the program is used for controlling equipment where the computer readable storage medium is located to execute the data synchronization method of the bank core system.
Specifically, the data synchronization method of the bank core system comprises the following steps:
step S201, first data synchronization request information in a message middleware is called, data of the first data synchronization request information is analyzed to obtain second data synchronization request information, so that the second data synchronization request information can be directly executed by a target bank core system, wherein the first data synchronization request information is information for requesting to synchronize service data to be synchronized as target service data, the service data to be synchronized is service data different from service data in a source bank core system in the target bank core system, and the target service data is service data corresponding to the service data to be synchronized in the source bank core system;
step S202, the second data synchronization request information is sent to the target bank core system to update the service data to be synchronized in the database of the target bank core system.
In one embodiment of the present application, retrieving first data synchronization request information in a message middleware includes: and calling the first data synchronization request information in the message middleware in real time.
In one embodiment of the present application, after the sending of the second data synchronization request information to the target banking core system, the method further includes: determining whether the service data to be synchronized is successfully synchronized into target service data; under the condition that the service data to be synchronized is successfully synchronized into target service data, determining that data synchronization work is completed, wherein the data synchronization work is used for representing the work of updating the service data to be synchronized in a database of a target bank core system; and under the condition that the service data to be synchronized is not successfully synchronized as target service data, storing the first data synchronization request information in the message middleware into a retry queue of the message middleware, and calling the first data synchronization request information of the retry queue, wherein the retry queue is the first data synchronization request information which needs to be retried in the message middleware.
In one embodiment of the present application, the retrieving the first data synchronization request information of the retry queue includes: after the second data synchronization request information is sent to the target bank core system, the first data synchronization request information of the retry queue is called when a first preset time elapses; and recording the retry times of the first data synchronization request information.
In an embodiment of the present application, after recording the number of retries of the first data synchronization request information, the method further includes: and if the retry number is greater than or equal to a predetermined number, moving the first data synchronization request information of the retry queue to a dead message queue of the message middleware, wherein the dead message queue is a queue which does not call information any more.
In an embodiment of the present application, after recording the number of retries of the first data synchronization request information, the method further includes: and under the condition that the service data to be synchronized is determined to be synchronized into target service data and a second preset time is passed, the first data synchronization request information in the retry queue is called.
In an embodiment of the present application, the first data synchronization request information and the second data synchronization request information are both sql object serialization information.
The embodiment of the invention provides a processor, which is used for running a program, wherein the data synchronization method of the bank core system is executed when the program runs.
Specifically, the data synchronization method of the bank core system comprises the following steps:
Step S201, first data synchronization request information in a message middleware is called, data of the first data synchronization request information is analyzed to obtain second data synchronization request information, so that the second data synchronization request information can be directly executed by a target bank core system, wherein the first data synchronization request information is information for requesting to synchronize service data to be synchronized as target service data, the service data to be synchronized is service data different from service data in a source bank core system in the target bank core system, and the target service data is service data corresponding to the service data to be synchronized in the source bank core system;
step S202, the second data synchronization request information is sent to the target bank core system to update the service data to be synchronized in the database of the target bank core system.
In one embodiment of the present application, retrieving first data synchronization request information in a message middleware includes: and calling the first data synchronization request information in the message middleware in real time.
In one embodiment of the present application, after the sending of the second data synchronization request information to the target banking core system, the method further includes: determining whether the service data to be synchronized is successfully synchronized into target service data; under the condition that the service data to be synchronized is successfully synchronized into target service data, determining that data synchronization work is completed, wherein the data synchronization work is used for representing the work of updating the service data to be synchronized in a database of a target bank core system; and under the condition that the service data to be synchronized is not successfully synchronized as target service data, storing the first data synchronization request information in the message middleware into a retry queue of the message middleware, and calling the first data synchronization request information of the retry queue, wherein the retry queue is the first data synchronization request information which needs to be retried in the message middleware.
In one embodiment of the present application, the retrieving the first data synchronization request information of the retry queue includes: after the second data synchronization request information is sent to the target bank core system, the first data synchronization request information of the retry queue is called when a first preset time elapses; and recording the retry times of the first data synchronization request information.
In an embodiment of the present application, after recording the number of retries of the first data synchronization request information, the method further includes: and if the retry number is greater than or equal to a predetermined number, moving the first data synchronization request information of the retry queue to a dead message queue of the message middleware, wherein the dead message queue is a queue which does not call information any more.
In an embodiment of the present application, after recording the number of retries of the first data synchronization request information, the method further includes: and under the condition that the service data to be synchronized is determined to be synchronized into target service data and a second preset time is passed, the first data synchronization request information in the retry queue is called.
In an embodiment of the present application, the first data synchronization request information and the second data synchronization request information are both sql object serialization information.
The embodiment of the invention provides equipment, which comprises a processor, a memory and a program stored in the memory and capable of running on the processor, wherein the processor realizes at least the following steps when executing the program: the method comprises the steps of calling first data synchronization request information in a message middleware, analyzing data of the first data synchronization request information to obtain second data synchronization request information, and enabling the second data synchronization request information to be directly executed by a target bank core system, wherein the first data synchronization request information is information for requesting to synchronize service data to be synchronized to be target service data, the service data to be synchronized is service data different from service data in a source bank core system in the target bank core system, and the target service data is service data corresponding to the service data to be synchronized in the source bank core system; and sending the second data synchronization request information to the target bank core system so as to update the business data needing to be synchronized in the database of the target bank core system. The device herein may be a server, PC, PAD, cell phone, etc.
In one embodiment of the present application, retrieving first data synchronization request information in a message middleware includes: and calling the first data synchronization request information in the message middleware in real time.
In one embodiment of the present application, after the sending of the second data synchronization request information to the target banking core system, the method further includes: determining whether the service data to be synchronized is successfully synchronized into target service data; under the condition that the service data to be synchronized is successfully synchronized into target service data, determining that data synchronization work is completed, wherein the data synchronization work is used for representing the work of updating the service data to be synchronized in a database of a target bank core system; and under the condition that the service data to be synchronized is not successfully synchronized as target service data, storing the first data synchronization request information in the message middleware into a retry queue of the message middleware, and calling the first data synchronization request information of the retry queue, wherein the retry queue is the first data synchronization request information which needs to be retried in the message middleware.
In one embodiment of the present application, the retrieving the first data synchronization request information of the retry queue includes: after the second data synchronization request information is sent to the target bank core system, the first data synchronization request information of the retry queue is called when a first preset time elapses; and recording the retry times of the first data synchronization request information.
In an embodiment of the present application, after recording the number of retries of the first data synchronization request information, the method further includes: and if the retry number is greater than or equal to a predetermined number, moving the first data synchronization request information of the retry queue to a dead message queue of the message middleware, wherein the dead message queue is a queue which does not call information any more.
In an embodiment of the present application, after recording the number of retries of the first data synchronization request information, the method further includes: and under the condition that the service data to be synchronized is determined to be synchronized into target service data and a second preset time is passed, the first data synchronization request information in the retry queue is called.
In an embodiment of the present application, the first data synchronization request information and the second data synchronization request information are both sql object serialization information.
The present application also provides a computer program product adapted to perform a program initialized with at least the following method steps when executed on a data processing device: the method comprises the steps of calling first data synchronization request information in a message middleware, analyzing data of the first data synchronization request information to obtain second data synchronization request information, and enabling the second data synchronization request information to be directly executed by a target bank core system, wherein the first data synchronization request information is information for requesting to synchronize service data to be synchronized to be target service data, the service data to be synchronized is service data different from service data in a source bank core system in the target bank core system, and the target service data is service data corresponding to the service data to be synchronized in the source bank core system; and sending the second data synchronization request information to the target bank core system so as to update the business data needing to be synchronized in the database of the target bank core system.
In one embodiment of the present application, retrieving first data synchronization request information in a message middleware includes: and calling the first data synchronization request information in the message middleware in real time.
In one embodiment of the present application, after the sending of the second data synchronization request information to the target banking core system, the method further includes: determining whether the service data to be synchronized is successfully synchronized into target service data; under the condition that the service data to be synchronized is successfully synchronized into target service data, determining that data synchronization work is completed, wherein the data synchronization work is used for representing the work of updating the service data to be synchronized in a database of a target bank core system; and under the condition that the service data to be synchronized is not successfully synchronized as target service data, storing the first data synchronization request information in the message middleware into a retry queue of the message middleware, and calling the first data synchronization request information of the retry queue, wherein the retry queue is the first data synchronization request information which needs to be retried in the message middleware.
In one embodiment of the present application, the retrieving the first data synchronization request information of the retry queue includes: after the second data synchronization request information is sent to the target bank core system, the first data synchronization request information of the retry queue is called when a first preset time elapses; and recording the retry times of the first data synchronization request information.
In an embodiment of the present application, after recording the number of retries of the first data synchronization request information, the method further includes: and if the retry number is greater than or equal to a predetermined number, moving the first data synchronization request information of the retry queue to a dead message queue of the message middleware, wherein the dead message queue is a queue which does not call information any more.
In an embodiment of the present application, after recording the number of retries of the first data synchronization request information, the method further includes: and under the condition that the service data to be synchronized is determined to be synchronized into target service data and a second preset time is passed, the first data synchronization request information in the retry queue is called.
In an embodiment of the present application, the first data synchronization request information and the second data synchronization request information are both sql object serialization information.
The present application provides an electronic device comprising one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising a data synchronization method for executing any one of the banking core systems described above.
It will be appreciated by those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, etc., such as Read Only Memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
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 one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises an element.
From the above description, it can be seen that the above embodiments of the present application achieve the following technical effects:
1) According to the data synchronization method of the bank core system, the first data synchronization request information in the message middleware is called, the data of the first data synchronization request information is analyzed to obtain the second data synchronization request information, and then the second data synchronization request information is sent to the target bank core system to update the business data needing to be synchronized in the database of the target bank core system.
2) The data synchronization method of the bank core system has the advantages that the dependence on cluster resources is small, deployment scale can be determined according to actual data magnitude, the deployment scale can be quickly stretched, the actual landing is more convenient, transaction information is adopted in data production, a retry mechanism is provided for data consumption, the final consistency of the data is ensured, the dependence between heterogeneous systems is reduced by decoupling the source bank core system and the target bank core system through middleware, and the near-real-time synchronization efficiency can be achieved.
The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the same, but rather, various modifications and variations may be made by those skilled in the art. Any synchronization, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.
Claims (10)
1. A method for synchronizing data of a banking core system, comprising:
the method comprises the steps of calling first data synchronization request information in a message middleware, analyzing data of the first data synchronization request information to obtain second data synchronization request information, and enabling the second data synchronization request information to be directly executed by a target bank core system, wherein the first data synchronization request information is information for requesting to synchronize service data to be synchronized to be target service data, the service data to be synchronized is service data different from service data in a source bank core system in the target bank core system, and the target service data is service data corresponding to the service data to be synchronized in the source bank core system;
And sending the second data synchronization request information to the target bank core system to update the business data needing synchronization in the database of the target bank core system.
2. The method of claim 1, wherein retrieving the first data synchronization request information in the message middleware comprises:
and calling the first data synchronization request information in the message middleware in real time.
3. The method of claim 1, wherein after sending the second data synchronization request information to the target banking core system, the method further comprises:
determining whether the service data to be synchronized is successfully synchronized into target service data;
under the condition that the service data to be synchronized is successfully synchronized into target service data, determining that data synchronization work is completed, wherein the data synchronization work is used for representing the work of updating the service data to be synchronized in a database of a target bank core system;
and under the condition that the service data to be synchronized is not successfully synchronized as target service data, storing the first data synchronization request information in the message middleware into a retry queue of the message middleware, and calling the first data synchronization request information of the retry queue, wherein the retry queue is the first data synchronization request information which needs to be retried in the message middleware.
4. The method of claim 3, wherein invoking the first data synchronization request information of the retry queue comprises:
after the second data synchronization request information is sent to the target bank core system, under the condition that a first preset time passes, the first data synchronization request information of the retry queue is called;
and recording the retry times of the first data synchronization request information.
5. The method of claim 4, wherein after recording the number of retries of the first data synchronization request information, the method further comprises:
and under the condition that the retry time is greater than or equal to the preset time, moving the first data synchronization request information of the retry queue to a dead message queue of the message middleware, wherein the dead message queue is a queue which does not call information any more.
6. The method of claim 4, wherein after recording the number of retries of the first data synchronization request information, the method further comprises:
and under the condition that the service data to be synchronized is determined to be synchronized into target service data and a second preset time is passed, the first data synchronization request information in the retry queue is called.
7. The method of claim 1, wherein the first data synchronization request information and the second data synchronization request information are both sql object serialization information.
8. A data synchronization device for a banking core system, comprising:
the first processing unit is used for retrieving first data synchronization request information in the message middleware, analyzing data of the first data synchronization request information to obtain second data synchronization request information, so that the second data synchronization request information can be directly executed by a target bank core system, wherein the first data synchronization request information is information for requesting to synchronize service data to be synchronized as target service data, the service data to be synchronized is service data different from service data in a source bank core system in the target bank core system, and the target service data is service data corresponding to the service data to be synchronized in the source bank core system;
and the second processing unit is used for sending the second data synchronization request information to the target bank core system so as to update the business data which need to be synchronized in the database of the target bank core system.
9. A computer readable storage medium, characterized in that the computer readable storage medium comprises a stored program, wherein the program when run controls a device in which the computer readable storage medium is located to perform the data synchronization method of the banking core system of any one of claims 1 to 7.
10. An electronic device, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising a data synchronization method for performing the banking core system of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211698001.9A CN116303760A (en) | 2022-12-28 | 2022-12-28 | Data synchronization method and device of bank core system and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211698001.9A CN116303760A (en) | 2022-12-28 | 2022-12-28 | Data synchronization method and device of bank core system and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116303760A true CN116303760A (en) | 2023-06-23 |
Family
ID=86780395
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211698001.9A Pending CN116303760A (en) | 2022-12-28 | 2022-12-28 | Data synchronization method and device of bank core system and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116303760A (en) |
-
2022
- 2022-12-28 CN CN202211698001.9A patent/CN116303760A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2019262823B2 (en) | Input and output schema mappings | |
| US10498625B1 (en) | Distributed testing service | |
| US10621049B1 (en) | Consistent backups based on local node clock | |
| US7467389B2 (en) | System and methodology providing service invocation for occasionally connected computing devices | |
| US8204870B2 (en) | Unwired enterprise platform | |
| CN111177161B (en) | Data processing method, device, computing equipment and storage medium | |
| CN102880503A (en) | Data analysis system and data analysis method | |
| CN108536778A (en) | A kind of data application shared platform and method | |
| CN112394947A (en) | Information system based on micro-service architecture | |
| CN111177237B (en) | Data processing system, method and device | |
| CN113542390B (en) | Internet of things equipment management method and system adopting memory data model | |
| CN105808354B (en) | The method for setting up interim Hadoop environment using wlan network | |
| CN116954944A (en) | Distributed data stream processing method, device and equipment based on memory grid | |
| CN112491943A (en) | Data request method, device, storage medium and electronic equipment | |
| CN116303760A (en) | Data synchronization method and device of bank core system and electronic equipment | |
| CN114969199A (en) | Method, device and system for processing remote sensing data and storage medium | |
| CN113641760A (en) | Data synchronization method and device | |
| CN111159004A (en) | Hadoop cluster simulation test method and device and storage medium | |
| CN115811546B (en) | System and method for realizing network collaborative distributed processing by scientific and technological service | |
| CN114268661B (en) | Service scheme deployment method, device, system and equipment | |
| Zheng et al. | Research and Implementation of Importing Distributed Cluster Data into Cloud Platform Based on JMS | |
| CN117032876A (en) | Program data access method and device, storage medium and electronic device | |
| CN115757587A (en) | Heterogeneous data source integration method and device, electronic equipment and storage medium | |
| CN115080664A (en) | Data synchronization method, system and computer readable storage medium | |
| CN116204120A (en) | Multi-cluster data searching method, device and computer readable storage medium |
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 |