CN116226080A - Data migration method, device, electronic equipment and storage medium - Google Patents

Data migration method, device, electronic equipment and storage medium Download PDF

Info

Publication number
CN116226080A
CN116226080A CN202211666296.1A CN202211666296A CN116226080A CN 116226080 A CN116226080 A CN 116226080A CN 202211666296 A CN202211666296 A CN 202211666296A CN 116226080 A CN116226080 A CN 116226080A
Authority
CN
China
Prior art keywords
user request
application
topic
identification information
sending
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
Application number
CN202211666296.1A
Other languages
Chinese (zh)
Inventor
马新悦
***
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Picc Information Technology Co ltd
Original Assignee
Picc Information Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Picc Information Technology Co ltd filed Critical Picc Information Technology Co ltd
Priority to CN202211666296.1A priority Critical patent/CN116226080A/en
Publication of CN116226080A publication Critical patent/CN116226080A/en
Pending legal-status Critical Current

Links

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/21—Design, administration or maintenance of databases
    • G06F16/214—Database migration support
    • 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/25—Integrating or interfacing systems involving database management systems
    • G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application discloses a data migration method, a device, electronic equipment and a storage medium, wherein the method comprises the following steps: under the condition that a user request to be sent to a first application is monitored, sending the user request to the first application and copying the user request, wherein the user request carries identification information, and the identification information is used for indicating reading of the user request or migration of the user request; and according to the identification information, controlling the second application to read the copied user request or send the copied user request to a third application and writing the copied user request into a target database corresponding to the third application, wherein the target database comprises the full data of the source database corresponding to the first application. The embodiment ensures the continuity of the service in the data migration process.

Description

Data migration method, device, electronic equipment and storage medium
Technical Field
The application belongs to the technical field of data migration, and particularly relates to a data migration method, a data migration device, electronic equipment and a storage medium.
Background
Data migration is a difficulty in the process of application system reconstruction and technical transformation. Currently in a database migration scenario, data of a source library is typically migrated to a target library at one time, but a service outage window is required, and the size of the window depends on the time of full data migration.
In the above scheme, when the data volume is large, the whole migration process may take several days, which results in a long service downtime and cannot guarantee service continuity.
Disclosure of Invention
The embodiment of the application provides a data migration method, a data migration device, electronic equipment and a storage medium, which are used for solving the problem that service continuity cannot be guaranteed in a data migration process in the related technology.
In a first aspect, an embodiment of the present application provides a data migration method, including:
under the condition that a user request to be sent to a first application is monitored, sending the user request to the first application and copying the user request, wherein the user request carries identification information, and the identification information is used for indicating reading of the user request or migration of the user request;
and according to the identification information, controlling the second application to read the copied user request or send the copied user request to a third application and writing the copied user request into a target database corresponding to the third application, wherein the target database comprises the full data of the source database corresponding to the first application.
In a second aspect, an embodiment of the present application further provides a data migration apparatus, including:
the sending module is used for sending the user request to the first application and copying the user request under the condition that the user request to be sent to the first application is monitored, wherein the user request carries identification information, and the identification information is used for indicating reading of the user request or migration of the user request;
and the processing module is used for controlling the second application to read the copied user request or send the copied user request to a third application and writing the copied user request into a target database corresponding to the third application according to the identification information, wherein the target database comprises the full data of the source database corresponding to the first application.
In a third aspect, embodiments of the present application provide an electronic device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction implementing the steps of the method according to the first aspect when executed by the processor.
In a fourth aspect, embodiments of the present application provide a readable storage medium having stored thereon a program or instructions which when executed by a processor implement the steps of the method according to the first aspect.
In the scheme provided by the embodiment of the application, under the condition that the user request to be sent to the first application is monitored, the user request is sent to the first application and copied, wherein the user request carries identification information, and the identification information is used for indicating reading or migration of the user request; according to the identification information, the second application is controlled to read the copied user request, or the copied user request is sent to a third application and written into a target database corresponding to the third application, and the target database comprises the full data of the source database corresponding to the first application, so that the user request is copied while the user request is continuously sent to the first application for processing, and the copied user request is read or written into the target database according to the requirement, the incremental data is migrated into the target database, the continuity of service processing is ensured, and the problem that the service continuity cannot be ensured in the data migration process is solved.
Drawings
FIG. 1 is a schematic flow chart of a data migration method in an embodiment of the present application;
FIG. 2 is a process schematic of a data migration method in an embodiment of the present application;
FIG. 3 is a schematic structural diagram of a data migration device according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. 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, are intended to be within the scope of the present application.
The terms first, second and the like in the description and in the claims, 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, as appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type and not limited to the number of objects, e.g., the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.
The data migration method provided by the embodiment of the application is described in detail below through specific embodiments and application scenarios thereof with reference to the accompanying drawings.
Fig. 1 illustrates a data migration method provided by an embodiment of the present invention, which may be performed by an electronic device, which may include: server and/or terminal device. In other words, the method may be performed by software or hardware installed in the electronic device, the method comprising the steps of:
step 101: in case a user request to be sent to a first application is monitored, sending the user request to the first application and copying the user request.
In particular, the user request may be a hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP) request.
In case a user request to be sent to the first application is monitored, the user request may be sent to the first application, thereby enabling processing of the user request by the first application. The first application corresponds to an active database, and the active database stores full data of the current time.
In addition, the user request needs to be replicated while the user request is sent to the first application, and the user request carries identification information, where the identification information is used to indicate reading of the user request or migration of the user request. This enables the copied user request to be read or migrated by the identification information carried by the user request.
Step 102: and according to the identification information, controlling the second application to read the copied user request, or sending the copied user request to a third application and writing the copied user request into a target database corresponding to the third application.
Specifically, if the identification information is used for indicating to read the user request, the second application may be controlled to read the copied user request; if the identification information is used for indicating to migrate the user request, the copied user request can be sent to the third application and written into a target database corresponding to the third application, so that the newly added user request can be smoothly migrated into the target database under the condition that the service is not perceived. And the reading or writing processing process of the data is realized through different information indicated by the identification information, so that different service requirements are met.
In addition, the second application may be a test application, and of course the test application corresponds to a test database, and in this case, the pressure test or the functional verification of the system may be implemented by the second application.
The service attributes of the third application and the first application can be the same, so that the request result fed back by the third application and the request result fed back by the first application can be the same, and further reconstruction of an application system can be realized.
It should be noted that, the target database includes the full data of the source database corresponding to the first application, which enables the data integrity of the target database to be completed after the newly added user request is migrated to the target database.
In the sample embodiment, under the condition that the user request to be sent to the first application is monitored, the user request is sent to the first application and copied, the second application is controlled to read the copied user request according to the identification information carried by the user request, or the copied user request is sent to a third application and written into a target database corresponding to the third application, and the target database comprises the full data of the source database corresponding to the first application, so that the user request is copied while the user request is continuously sent to the first application for processing, and the copied user request is read according to the requirement
Or writing the data into the target database, thereby realizing the migration of the newly added data into the target database, ensuring the continuity of service processing and solving the problem that the data migration process can not ensure the continuity of service.
In addition, the embodiment can implement the copy process of the user request by means of openrest+lua+kafka of the application layer. Specifically, in one embodiment, the sending the user request to the first application and copying the user request includes the following steps:
and sending the user request to the first application through OpenResity, and sending the user request to a first Topic Topic or a second Topic in Kafka according to the identification information 0, wherein the first Topic is used for storing the user request to be read, and the second Topic is used for storing the user request to be migrated.
Specifically, openResity is a high-performance global Wide area network (Web) platform based on Nginx and Lua, and a large number of fine Lua libraries, third party modules and most 5 dependent items are integrated in the platform, so that dynamic Web applications, web services and dynamic gateways which can process ultrahigh concurrency and extremely high expansibility are conveniently built.
In the nginx system, the embodiment can configure the ngx.location.capture_multi of the openrest to realize the concurrent copy of the same user request. The configuration text of the openrest can be in the embodiment
Setting related parameters in the component, such as connection timeout time, sending timeout time, reading timeout time, maintaining 0 high availability timeout time, size of a connection pool, size of a buffer memory and the like, acquiring a message header and a message body of a user request, copying the request message body by using a capture_multi API, and forwarding the user request to a first application.
In addition, the embodiment can also create a Kafka producer of the openrest and formulate the elimination of the producer
A message broker list (broker list) of the Kafka cluster in the form of a message and creates a first Topic for storing user requests to be read 5 and a second Topic for storing user requests to be migrated. This enables the embodiment to send a user request to the first application through openResity, send a user request indicating that the identification information is read to the first Topic in Kafka through openResity, and send a user request indicating that the identification information is migrated to the second Topic, thereby realizing the copying process of the data in the manner of openResity+lua+kafka.
In addition, in one embodiment, according to the identification information, controlling the second application to read the copied user request or send the copied user request to the third application and write the copied user request into the target database corresponding to the third application includes:
and controlling the second application to read the user request from the first Topic, or sending the user request in the second Topic to a third application and writing the user request in the second Topic into a target database corresponding to the third application.
Specifically, since the first Topic is used for storing the user request to be read, and the second Topic is used for storing the user request to be migrated, the second application can be controlled to read the user request from the first Topic, or send the user request in the second Topic to the third application and write the user request in the target database corresponding to the third application, so that the user requests with different indication types are obtained from different Topic, and the user request to be read is prevented from being written in the target database or the user request to be migrated is prevented from being read to the second application.
In addition, in order to ensure the processing sequence of the request of the same service primary key, in one embodiment, the first Topic and the second Topic are both partitioned in advance according to service primary key information, and the user request also carries service primary key information of the user;
at this time, the sending the user request to the first Topic or the second Topic in Kafka according to the identification information includes: and sending the user request to the partition corresponding to the service primary key information in the first Topic or the second Topic according to the service primary key information.
Specifically, the service primary key information may include a user identifier, a user service list number, and the like, and of course, the service primary key information corresponding to each user has uniqueness.
According to the method, the user request is sent to the partition corresponding to the business primary key information in the first Topic or the second Topic according to the business primary key information, so that only one business request corresponding to the business primary key is stored in each partition, and the processing sequence of the request of the same business primary key can be ensured through the characteristic of first-in first-out of the message in the partition.
The present embodiment will be specifically described with reference to fig. 2.
As shown in fig. 2, assuming that the application system is an nginx system, when the nginx system receives a user request, the user request can be sent to the first application through openResity, and the first application can query a request result of the user request from a source database at this time;
the embodiment can create a Kafka producer of the openrest, formulate a message format of the producer, a brooker list of a Kafka cluster, a Kafka consumer, and create a first Topic for storing user requests to be read and a second Topic for storing user requests to be migrated. The user request carries identification information, the identification information is used for indicating the user request to be read or the user request to be migrated, at the moment, the user request can be copied to a first Topic or a second Topic in Kafka through openResity, the second application is controlled to read the user request from the first Topic according to the identification information, or an application program interface (Application Program Interface, API) related to a third application is called through a Kafka message, and the user request in the second Topic is sent to the third application and written into a target database corresponding to the third application. Specifically, the second application may be a test application, and a test database is corresponding to the second application, so as to implement a pressure or function test of the reconfiguration application system.
It should be noted that the target database includes the full data of the source database, thereby ensuring the integrity of the target database.
In this way, the embodiment realizes that the user request is copied while the user request is continuously sent to the first application for processing, and reads or writes the copied user request into the target database according to the requirement, thereby realizing that incremental data is migrated into the target database, ensuring continuity of service processing, being capable of automatically adapting to data model change and application logic optimization in the processes of application system reconstruction, data migration and the like, and further solving the problems of data link redundancy and data processing logic repetition in the data migration process.
Fig. 3 is a schematic structural diagram of a data migration apparatus according to an embodiment of the present invention. As shown in fig. 3, the data migration apparatus includes:
a sending module 301, configured to send a user request to a first application and copy the user request if a user request to be sent to the first application is detected, where the user request carries identification information, where the identification information is used to indicate reading the user request or migrating the user request;
and the processing module 302 is configured to control, according to the identification information, the second application to read the copied user request, or send the copied user request to a third application and write the copied user request into a target database corresponding to the third application 5, where the target database includes the full data of the source database corresponding to the first application.
In one embodiment, the sending module 301 is configured to send the user request to the first application through openResty, and send the user request to Kafka according to the identification information
A first Topic for storing a user request 0 to be read or a second Topic for storing a user request to be migrated.
In one embodiment, the first Topic and the second Topic are each partitioned in advance according to service primary key information, and the user request further carries service primary key information of the user;
the sending module is configured to send the user request to a partition corresponding to the service primary key information in the first Topic or the second Topic according to the service primary key information.
5 in one embodiment, the processing module is configured to control the second application to read the user request from the first Topic, or send the user request in the second Topic to a third application and write the user request in the third application into a target database corresponding to the third application.
The data migration apparatus provided in this embodiment of the present application can implement each process implemented by the method embodiment of fig. 1-2, and in order to avoid repetition, a description is omitted here.
0, it should be noted that, in the present specification, the embodiment about the data migration apparatus and the embodiment about the data migration method in the present specification are based on the same inventive concept, so the specific implementation about the embodiment about the data migration apparatus may refer to the corresponding implementation about the embodiment about the data migration method, and the repetition is omitted.
The data migration device in the embodiment of the present application may be a device, or may be a component in a terminal, a integrated circuit 5, or a chip. The device may be a mobile electronic device or a non-mobile electronic device. By way of example, the mobile electronic device may be a cell phone, tablet computer, notebook computer, palm computer, vehicle-mounted electronic device, wearable device, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), netbook or personal digital assistant (personal digital assistant, PDA), etc., and the non-mobile electronic device may be a server, network attached storage (Network Attached Storage, NAS), personal computer (personal computer, PC), television (TV), teller machine or self-service machine, etc., and the embodiments of the present application are not limited in particular.
The data migration device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
Based on the same technical concept, the embodiment of the present application further provides an electronic device, where the electronic device is configured to perform the above data migration method, and fig. 4 is a schematic structural diagram of an electronic device implementing the embodiments of the present application. The electronic devices may be configured or configured to have a relatively large difference, and may include a processor (processor) 410, a communication interface (Communications Interface) 420, a memory (memory) 430, and a communication bus 440, where the processor 410, the communication interface 420, and the memory 430 perform communication with each other through the communication bus 440. The processor 410 may call a computer program stored on the memory 430 and executable on the processor 410 to perform the steps of:
under the condition that a user request to be sent to a first application is monitored, sending the user request to the first application and copying the user request, wherein the user request carries identification information, and the identification information is used for indicating reading of the user request or migration of the user request;
and according to the identification information, controlling the second application to read the copied user request, or sending the copied user request to a third application and writing the copied user request into a target database corresponding to the third application, wherein the target database comprises the full data of the source database corresponding to the first application.
In one embodiment, the sending the user request to the first application and replicating the user request includes: and sending the user request to the first application through OpenResity, and sending the user request to a first Topic Topic or a second Topic in Kafka according to the identification information, wherein the first Topic is used for storing the user request to be read, and the second Topic is used for storing the user request to be migrated.
In one embodiment, the first Topic and the second Topic are each partitioned in advance according to service primary key information, and the user request further carries service primary key information of the user;
the sending the user request to the first Topic or the second Topic in Kafka according to the identification information comprises the following steps: and sending the user request to the partition corresponding to the service primary key information in the first Topic or the second Topic according to the service primary key information.
In one embodiment, the controlling, according to the identification information, the second application to read the replicated user request, or sending the replicated user request to a third application and writing the replicated user request into a target database corresponding to the third application includes: and according to the identification information, controlling the second application to read the user request from the first Topic, or sending the user request in the second Topic to a third application and writing the user request in the second Topic into a target database corresponding to the third application.
The specific implementation steps can refer to the steps of the above data migration method embodiment, and the same technical effects can be achieved, so that repetition is avoided and no further description is provided here.
It should be noted that, the electronic device in the embodiment of the present application includes: a server, a terminal, or other devices besides a terminal.
The above electronic device structure does not constitute a limitation of the electronic device, and the electronic device may include more or less components than illustrated, or may combine some components, or may be different in arrangement of components, for example, an input unit, may include a graphics processor (Graphics Processing Unit, GPU) and a microphone, and a display unit may configure a display panel in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit includes at least one of a touch panel and other input devices. Touch panels are also known as touch screens. Other input devices may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.
The memory may be used to store software programs as well as various data. The memory may mainly include a first memory area storing programs or instructions and a second memory area storing data, wherein the first memory area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory may include volatile memory or nonvolatile memory, or the memory may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (ddr SDRAM), enhanced SDRAM (Enhanced SDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DRRAM).
The processor may include one or more processing units; optionally, the processor integrates an application processor that primarily processes operations involving an operating system, user interface, application programs, and the like, and a modem processor that primarily processes wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the foregoing data migration method embodiment, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.
Wherein the processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
The embodiment of the application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used for running a program or an instruction, implementing each process of the above method embodiment, and achieving the same technical effect, so as to avoid repetition, and not repeated here.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, chip systems, or system-on-chip chips, etc.
It should be noted that, in this document, 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 the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), including several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims (10)

1. A method of data migration, comprising:
under the condition that a user request to be sent to a first application is monitored, sending the user request to the first application and copying the user request, wherein the user request carries identification information, and the identification information is used for indicating reading of the user request or migration of the user request;
and according to the identification information, controlling the second application to read the copied user request, or sending the copied user request to a third application and writing the copied user request into a target database corresponding to the third application, wherein the target database comprises the full data of the source database corresponding to the first application.
2. The data migration method of claim 1, wherein said sending the user request to the first application and replicating the user request comprises:
and sending the user request to the first application through OpenResity, and sending the user request to a first Topic Topic or a second Topic in Kafka according to the identification information, wherein the first Topic is used for storing the user request to be read, and the second Topic is used for storing the user request to be migrated.
3. The data migration method according to claim 2, wherein the first Topic and the second Topic are each partitioned in advance according to service primary key information, and the user request further carries service primary key information of a user;
the sending the user request to the first Topic or the second Topic in Kafka according to the identification information comprises the following steps:
and sending the user request to the partition corresponding to the service primary key information in the first Topic or the second Topic according to the service primary key information.
4. The data migration method according to claim 2, wherein the controlling the second application to read the copied user request according to the identification information, or sending the copied user request to a third application and writing the copied user request into a target database corresponding to the third application includes:
and according to the identification information, controlling the second application to read the user request from the first Topic, or sending the user request in the second Topic to a third application and writing the user request in the second Topic into a target database corresponding to the third application.
5. A data migration apparatus, comprising:
the sending module is used for sending the user request to the first application and copying the user request under the condition that the user request to be sent to the first application is monitored, wherein the user request carries identification information, and the identification information is used for indicating reading of the user request or migration of the user request;
and the processing module is used for controlling the second application to read the copied user request according to the identification information, or sending the copied user request to a third application and writing the copied user request into a target database corresponding to the third application, wherein the target database comprises the full data of the source database corresponding to the first application.
6. The data migration apparatus according to claim 5, wherein the sending module is configured to send the user request to the first application through openredundancy, and send the user request to a first Topic or a second Topic in Kafka according to the identification information, where the first Topic is used for storing a user request to be read, and the second Topic is used for storing a user request to be migrated.
7. The data migration apparatus of claim 6, wherein the first Topic and the second Topic are each partitioned in advance according to service primary key information, and the user request further carries service primary key information of a user;
the sending module is configured to send the user request to a partition corresponding to the service primary key information in the first Topic or the second Topic according to the service primary key information.
8. The data migration apparatus of claim 6, wherein the processing module is configured to control the second application to read the user request from the first Topic, or send the user request in the second Topic to a third application and write the user request in the third application into a target database corresponding to the third application.
9. An electronic device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the data migration method of any one of claims 1-4.
10. A readable storage medium, characterized in that the readable storage medium has stored thereon a program or instructions which, when executed by a processor, implement the steps of the data migration method according to any one of claims 1-4.
CN202211666296.1A 2022-12-23 2022-12-23 Data migration method, device, electronic equipment and storage medium Pending CN116226080A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211666296.1A CN116226080A (en) 2022-12-23 2022-12-23 Data migration method, device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211666296.1A CN116226080A (en) 2022-12-23 2022-12-23 Data migration method, device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN116226080A true CN116226080A (en) 2023-06-06

Family

ID=86590144

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211666296.1A Pending CN116226080A (en) 2022-12-23 2022-12-23 Data migration method, device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116226080A (en)

Similar Documents

Publication Publication Date Title
CN111602120B (en) Displaying an indication of changes made to content at a source
CN108509207A (en) The cross-system of WEB application program is installed
CN106874328A (en) A kind of data processing method and equipment
CN110333919B (en) Method and equipment for presenting social object information
CN106648569A (en) Target serialization achieving method and device
US20170083387A1 (en) High-performance computing framework for cloud computing environments
CN110196680B (en) Data processing method, device and storage medium
CN109857573A (en) A kind of data sharing method, device, equipment and system
US20220164408A1 (en) System and method of integrating collaboration tools
CN102779076B (en) The method and apparatus of interprocess communication in a kind of browser
CN110618811B (en) Information presentation method and device
US11558321B2 (en) Integration of an email client with hosted applications
CN116226080A (en) Data migration method, device, electronic equipment and storage medium
US8892807B2 (en) Emulating a skip read command
CN114928620A (en) User information synchronization method, device, equipment, storage medium and program product
CN112597408B (en) System fusion method, device, equipment and storage medium
CN114564241A (en) Hardware device access method and device, computer device and storage medium
US20180090174A1 (en) Video generation of project revision history
CN105183491A (en) Cross-platform desktop GIS and starting method thereof
CN111125565A (en) Method and equipment for inputting information in application
US11736427B2 (en) Integration of client applications with hosted applications
CN116610880B (en) Method and device for realizing data visualization, electronic equipment and storage medium
CN112000563B (en) Recording method, device and equipment of user behaviors
US20220253458A1 (en) Method and device for synchronizing node data
CN117194344A (en) File management method and device and electronic equipment

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