Service migration method and device, equipment, storage medium and product

Abstract

The invention discloses a service migration method and device, equipment, a storage medium and a product, and relates to the technical field of data migration. The service migration method comprises the steps that a migration instruction triggered by a user on a foreground interface is received, and based on the migration instruction, service migration is carried out; a migration group selected by the user and a preset migration rule corresponding to the migration group are obtained, the migration group comprises at least one migration plan, and the migration plan corresponds to at least one client to be migrated; based on the preset migration rule, service data corresponding to the to-be-migrated client in the migration group is obtained, and the service data comprises core data influencing external application access; and migrating the business data to a target library in batches, and forbidding the access of the external application when the core data is migrated, so that the problem that the system is unavailable within a period of time during shutdown migration can be avoided.

Description

Technical Field

[0001] The present application relates to the field of data migration technology, and in particular to business migration methods, devices, equipment, storage media and products. Background Art

[0002] Business migration generally refers to the process of migrating a bank's existing business systems, data or services from one platform or environment to another.

[0003] In the related art, business migration is performed through downtime migration, but during the downtime migration, the system will be unavailable for a period of time. Summary of the invention

[0004] The main purpose of this application is to provide a business migration method, which aims to solve the problem of business migration through downtime migration. However, during downtime migration, the system will be unavailable for a period of time.

[0005] To achieve the above objectives, the present application proposes a service migration method, which includes:

[0006] Receiving a migration instruction triggered by a user on a front-end interface, and acquiring a migration group selected by the user and a preset migration rule corresponding to the migration group based on the migration instruction, wherein the migration group includes at least one migration plan, and the migration plan corresponds to at least one customer to be migrated;

[0007] Based on the preset migration rule, obtaining corresponding business data of the customer to be migrated in the migration group, wherein the business data includes core data affecting access of external applications;

[0008] The business data is migrated to the target database in batches, wherein the external application is prohibited from accessing the core data when the core data is being migrated.

[0009] In one embodiment, the step of migrating the business data to the target database in batches includes:

[0010] Determine the migration status of each migration plan and obtain a determination result;

[0011] If the judgment result is normal, an asynchronous thread is constructed for the business data corresponding to each of the to-be-migrated customers in the migration plan, and the business data corresponding to the asynchronous thread is migrated in batches to a target library storing the migrated business data.

[0012] In one embodiment, the business data includes customer data and account data, the account data includes the core data and non-core data, and the step of migrating the business data corresponding to the asynchronous thread in batches to a target library storing the migrated business data includes:

[0013] Pre-migrate the customer data and non-core data before a preset time to the target database;

[0014] After the pre-migration is completed, the status field in the routing table is set to a blocked state to prohibit the external application from accessing it, and based on the blocked state, the core data is formally migrated to the target database;

[0015] After the formal migration is completed, the status field is set to a valid state, and based on the valid state, the unmigrated data in the business data is post-migrated to the target library.

[0016] In one embodiment, the step of post-migrating the unmigrated data in the business data to the target database includes:

[0017] Migrating the unmigrated data in the customer data to the target database;

[0018] Migrate the unmigrated data in the account data to the target database.

[0019] In one embodiment, the step of migrating the business data to the target database in batches further includes:

[0020] If the status of the formal migration displayed on the front-end interface is normal and the status of the batch migration is abnormal, the migration status of the post-migration is judged, and the business data corresponding to the abnormal status is post-migrated to the target database again;

[0021] If the status of the formal migration displayed on the front-end interface is abnormal, the business data that has been migrated to the target database is deleted, and the deleted business data is migrated to the target database again in batches.

[0022] In one embodiment, after the step of acquiring the corresponding business data of the to-be-migrated customers in the migration group based on the preset migration rule, the following steps are performed:

[0023] Backing up the business data to obtain backup data;

[0024] After the formal migration is completed, the step of setting the status field to a valid state, and based on the valid state, post-migrating the unmigrated data in the business data to the target database comprises:

[0025] Acquire target data in the target library;

[0026] The backup data is compared with the target data to obtain a comparison result.

[0027] In addition, to achieve the above-mentioned purpose, the present application also proposes a service migration device, the service migration device comprising:

[0028] A receiving module, configured to receive a migration instruction triggered by a user on a front-end interface, and based on the migration instruction, obtain a migration group selected by the user and a preset migration rule corresponding to the migration group, wherein the migration group includes at least one migration plan, and the migration plan corresponds to at least one customer to be migrated;

[0029] An acquisition module, configured to acquire the corresponding business data of the customer to be migrated in the migration group based on the preset migration rule, wherein the business data includes core data affecting access of external applications;

[0030] The migration module is used to migrate the business data to the target database in batches, wherein when the core data is being migrated, the external application is prohibited from accessing it.

[0031] In addition, to achieve the above objectives, the present application also proposes a business migration device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the business migration method described above.

[0032] In addition, to achieve the above objectives, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the business migration method described above are implemented.

[0033] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the service migration method described above are implemented.

[0034] One or more technical solutions proposed in this application have at least the following technical effects:

[0035] Compared with the related art, in which business migration is mainly performed through downtime migration, but the system will be unavailable for a period of time during downtime migration, the present application receives a migration instruction triggered by a user on the front-end interface, and based on the migration instruction, obtains the migration group selected by the user and the preset migration rule corresponding to the migration group, wherein the migration group includes at least one migration plan, and the migration plan corresponds to at least one customer to be migrated; based on the preset migration rule, obtains the corresponding business data of the customer to be migrated in the migration group, wherein the business data includes core data that affects the access of external applications; migrates the business data to the target library in batches, wherein when the core data is migrated, the external application is prohibited from accessing. It can be understood that after obtaining the user's migration instruction, the present application obtains the migration group selected by the user and the preset migration rule based on the migration instruction, and obtains the business data corresponding to the customer to be migrated based on the preset migration rule, and migrates the business data to the target library in batches, and only when the core data is migrated, is the external application access prohibited, thereby avoiding the problem that the system will be unavailable for a period of time during downtime migration. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0038] Figure 1 A flowchart of the first embodiment of the method for business migration of this application is provided;

[0039] Figure 2 A diagram of the migration steps for a single customer for the business migration method of this application;

[0040] Figure 3 A specific flow chart of business migration for the business migration method of this application;

[0041] Figure 4 A flowchart of the second embodiment of the service migration method of this application is provided;

[0042] Figure 5 A brief flowchart of the service migration method provided in Example 2 of the present application;

[0043] Figure 6 This is a schematic diagram of the module structure of the service migration device according to an embodiment of the present application;

[0044] Figure 7 This is a schematic diagram of the device structure of the hardware operating environment involved in the business migration method in the embodiment of the present application.

[0045] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0046] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0047] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0048] The main solution of the embodiment of the present application is: receiving a migration instruction triggered by a user in a front-end interface, and based on the migration instruction, obtaining the migration group selected by the user and the preset migration rules corresponding to the migration group, wherein the migration group includes at least one migration plan, and the migration plan corresponds to at least one customer to be migrated; based on the preset migration rules, obtaining the corresponding business data of the customer to be migrated in the migration group, wherein the business data includes core data that affects access to external applications; migrating the business data to the target library in batches, wherein, when the core data is being migrated, access by external applications is prohibited.

[0049] In the related art, business migration is performed through downtime migration, but during the downtime migration, the system will be unavailable for a period of time.

[0050] After obtaining the user's migration instructions, the present application obtains the migration grouping and preset migration rules selected by the user based on the migration instructions, obtains the business data corresponding to the customers to be migrated based on the preset migration rules, and migrates the business data to the target database in batches. External application access is prohibited only when the core data is being migrated, thereby avoiding the problem of the system being unavailable for a period of time during downtime migration.

[0051] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, etc. The following takes the service migration device as an example to illustrate this embodiment and the following embodiments.

[0052] Based on this, the present application embodiment provides a service migration method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the service migration method of the present application.

[0053] In this embodiment, the service migration method includes steps S100 to S300:

[0054] Step S100, receiving a migration instruction triggered by a user on a front-end interface, and acquiring a migration group selected by the user and a preset migration rule corresponding to the migration group based on the migration instruction, wherein the migration group includes at least one migration plan, and the migration plan corresponds to at least one customer to be migrated;

[0055] It should be noted that the business migration device is provided with a front-end interface, which is provided with a migration operation interface and a migration interface. The migration operation is triggered in the migration interface, and various information during the migration process can also be viewed in the migration interface. The preset migration rules are the rules added by the operator on the migration operation page of the front-end interface, which indicate that this migration is performed according to the rules. After adding the migration rules, it is necessary to add a migration group and specify the migration rules for the group. After adding the migration group, multiple migration plans can be added under the group. These migration plans all follow the migration rules of the migration group. After that, migration batches can be added under the migration plan, and customers who meet the migration rules can be included in one click according to the corresponding migration rules.

[0056] It is understandable that after the pre-operation of the business migration device is completed, it switches to the migration interface. The operator queries all the migration groups to be migrated in the migration page, selects a migration group, and clicks execute to execute all the migration plans included in the migration group.

[0057] Specifically, the migration operation page is provided with a migration rule management module, and the migration rule management module is provided with a migration rule table. The operator can specify the number of regular accounts and the number of households of the customers to be migrated in this module, so that customers with similar data can be migrated in one migration plan, which makes the migration more flexible and efficient. The migration management module mainly provides the functions of adding, deleting and maintaining. The logic is relatively simple and it mainly performs maintenance operations on the records in the migration rule table.

[0058] The migration operation page is also equipped with a migration plan management module, which is equipped with a customer table to be migrated. The migration plan management module mainly provides several major functions, including adding, maintaining, deleting, including customers, removing customers, generating customer lists and clearing customer lists; adding, deleting and maintaining are usually operations on the records of the migration plan table in the database, and these functions are relatively simple; including customers mainly includes a certain customer in this migration, that is, adding a record to the customer table to be migrated, regardless of whether it meets the rules of this migration, and removing customers mainly deletes a certain customer from the customer table to be migrated; clearing the customer list can clear all customers in the customer table to be migrated that are linked to this migration plan at one time. Generally, this operation is performed because the wrong migration rules are associated, and then the customer list is to be regenerated; generating a customer list, at this time the system will send a request to WRTY (account migration application) through the TCP protocol to obtain a list of customers to be migrated that meet the rules of this migration, and synchronize these customers to the customer table to be migrated.

[0059] The migration operation page also has a migration group management module, which has a migration group management table. Migration groups are mainly proposed to better manage migration plans. There can be multiple migration plans under one migration group, and these migration plans are isolated from each other and do not affect each other. The addition, maintenance and deletion of this module are mainly carried out in the migration group management table, and its specific function is to better manage the groups. The function of associating migration plans can associate migration plans with the same migration rules as this group with this group, so that you can easily view which migration plans are under a certain migration group.

[0060] Step S200, based on the preset migration rule, obtaining the corresponding business data of the customer to be migrated in the migration group, wherein the business data includes core data that affects access to external applications;

[0061] It should be noted that core data refers to data that will affect the customer's core business. The business migration device determines the customer for this business migration and the business data corresponding to the customer according to the rules corresponding to the migration group selected by the user, wherein the business data includes core data that will affect the customer's core business.

[0062] Step S300: Migrate the business data to the target database in batches, wherein when the core data is being migrated, the external application is prohibited from accessing it.

[0063] It is understandable that the target database is the database used to store data in the target system after the business is migrated to the target system. The business migration device will migrate the business data corresponding to the customer to the target system in batches, and store the migrated business data in the target database of the target system. Only when the core data is migrated will the external request be stopped to perform business operations during the business migration process.

[0064] In a feasible implementation manner, step S300 includes the following steps:

[0065] Determine the migration status of each migration plan and obtain a determination result;

[0066] It should be noted that before executing each migration plan, the service migration device will automatically check the status of the current migration plan and obtain a judgment result.

[0067] If the judgment result is normal, an asynchronous thread is constructed for the business data corresponding to each of the to-be-migrated customers in the migration plan, and the business data corresponding to the asynchronous thread is migrated in batches to a target library storing the migrated business data.

[0068] It is understood that the normal state refers to the migration state of the migration plan is not interrupted. Asynchronous threads refer to threads that run independently of the main program execution flow (main thread) in a multi-threaded or multi-tasking environment; asynchronous threads can execute tasks without blocking the main thread, which is very useful for improving the responsiveness and efficiency of the program.

[0069] It should be noted that the business migration device will open a new asynchronous thread to process the migration for each customer in the group. Through the constructed asynchronous thread, the business data corresponding to the customer is migrated in batches to obtain the target library for storing the migrated business data. Please refer to Figure 2 , Figure 2 A diagram of the migration steps for a single customer.

[0070] Specifically, the migration process mainly includes WRTY pre-migration, DRTY (customer migration application) pre-migration, WMD (routing application) routing blocking, WRTY formal migration, WMD routing unblocking, WRTY and DRTY post-migration.

[0071] In particular, migration can be performed on a per-customer basis or as a whole batch.

[0072] In a feasible implementation manner, the step of migrating the business data corresponding to the asynchronous thread in batches to a target library storing the migrated business data includes:

[0073] Pre-migrate the customer data and non-core data before a preset time to the target database;

[0074] It is understandable that business data includes customer data and account data, and account data includes non-core data. The preset time is t-1 day. The business migration device pre-migrates customer data of different customers and account data before t-1 day to the target database through asynchronous threads.

[0075] It is understandable that after the pre-migration, the business migration device will also proofread the written business data and the data before writing to avoid data omission.

[0076] Specifically, the business migration equipment is pre-migrated through the DRTY application, and the WYZT application calls the TransferExecute migration method of the DRTY application through the HTTP protocol to migrate customer data, which mainly includes the following core steps: customer data query, customer data migration to the target system, and migration data verification. Customer data query is mainly performed through aggregate query in the form of database stored procedures to obtain a List data set. The step of migrating customer data to the target system is mainly performed through the Mybatis (framework) batch write operation, and the data in the List data set is written to the target system in Batch mode. The migration verification operation is mainly to compare the List data set of the source library with the List data set found in the target library. If they are consistent, subsequent operations are performed, otherwise an error is reported if they are inconsistent.

[0077] WRTY application pre-migration, WYZT application calls WRTY application's WrtyTrfCltPre migration method through TCP protocol to migrate customer data. WRTY pre-migration mainly migrates some transaction data before table T-1, which can reduce the impact of large data volume on customer business during formal migration. For specific migration steps, please refer to DRTY application pre-migration steps.

[0078] After the pre-migration is completed, the status field in the routing table is set to a blocked state to prohibit the external application from accessing it, and based on the blocked state, the core data is formally migrated to the target database;

[0079] It should be noted that the blocking state refers to the state in which an error is displayed when searching for routing information. After completing the pre-migration, the business migration device will set the status field in the routing table of the routing application to the blocking state, prohibiting external applications from performing business operations. After the routing table field is set, the core data in the account data is migrated to the target database through an asynchronous thread. The migration of core data is within 200ms, and customers who perform business operations will hardly feel it.

[0080] Specifically, the WYZT application calls the WrtCardRouterLock (route lock) of the WMD application through the HTTP protocol to block the route. WMD will set the status field in the routing table to the blocked state through this method. When the peripheral application queries the corresponding routing information through WMD, if it is in the blocked state, it will report an error, preventing external requests from performing business operations during the migration process, resulting in data inconsistency.

[0081] The WYZT application calls the WrtyTrfCltPrc migration method of the WRTY application through the TCP protocol to migrate customer data. The data officially migrated by WRTY will affect the customer's core business, so it needs to be migrated after the WMD blocks the route. For the core migration steps, refer to the DRTY application pre-migration.

[0082] After the formal migration is completed, the status field is set to a valid state, and based on the valid state, the unmigrated data in the business data is post-migrated to the target library.

[0083] It is understandable that the normal status will be displayed when searching for routing information in the valid state. The data that has not been migrated refers to the historical data and the data that has no impact on the core business. After completing the formal migration, the business migration device will set the status field in the routing table of the routing application from the blocked state to the valid state, and after the setting, through the asynchronous thread, the historical data in the business data and the data that has no impact on the core business will be migrated to the target database. Please refer to Figure 3 , Figure 3 Provides a specific flow chart for business migration.

[0084] Specifically, WMD unblocks the route, and the WYZT application calls the WrtCardRouterUpdate route blocking method of the WMD application through the HTTP protocol. WMD will set the route status corresponding to the customer to be migrated in the routing table to a valid state. At this time, the customer can go to the new database to process business.

[0085] WRTY and DRTY post-migration, WYZT application calls WRTY's WrtyTrfCltActPst and DRTY application's TransferBackExecute migration method through HTTP / TCP protocol. Post-migration mainly migrates historical data that has no impact on core business. The whole process is idempotent and supports reentrant operations. Please refer to Figure 4 , Figure 4 This is a business migration architecture diagram.

[0086] In a feasible implementation manner, the step of post-migrating the unmigrated data in the business data to the target database includes:

[0087] Migrating the unmigrated data in the customer data to the target database;

[0088] It should be noted that the data that has not been migrated includes customer data and account data. After the pre-migration and formal migration, the business migration device needs to check and clear the original business data, and migrate the customer data that has not been migrated in the original business data to the target database.

[0089] Migrate the unmigrated data in the account data to the target database.

[0090] It is understandable that after the pre-migration and the formal migration, the business migration device needs to migrate the account data that has not been migrated to the target database to ensure the complete migration of the data.

[0091] In this implementation, the business migration device first migrates data that has no impact on business operations by migrating in batches, and only stops business operations when migrating core data. The migration takes less than 200ms and is almost imperceptible to customers performing business operations, thereby improving the efficiency of business migration. The migrated data is migrated after the formal migration to ensure the data integrity of the business migration.

[0092] The present application embodiment provides a service migration method, referring to Figure 5 , Figure 5 This is a flow chart of the second embodiment of the service migration method of the present application.

[0093] In a feasible implementation manner, step S300 further includes the following steps A10 to A20:

[0094] Step A10: If the status of the formal migration displayed on the front-end interface is normal and the status of the batch migration is abnormal, the migration status of the post-migration is judged, and the business data corresponding to the abnormal status is post-migrated to the target database again;

[0095] It should be noted that the service migration device is also provided with a migration exception retry processing module, which monitors the migration status of each migration plan to ensure the normal migration process. When the service migration device detects that the migration status is abnormal, if the status of the formal migration is normal, it checks the status of the post-migration. If the post-migration status is abnormal, it tries to re-execute the abnormal post-migration steps.

[0096] Specifically, WRTY formal migration is completed but exception handling is required, that is, the post-migration reports an error. However, because the post-migration implements idempotence, retries can be used to execute the post-migration again to achieve exception handling. WMD route rollback mainly rolls back the route changes in the source database to the original state. DRTY post-migration retry mainly changes according to the migration status. If the status is S, it returns directly, because the S status indicates that the post-migration has been completed and no further operation is required. If the status is E, it indicates that there is a failed step, and the post-migration retry logic is executed again.

[0097] Step A20: If the status of the formal migration displayed on the front-end interface is abnormal, the business data that has been migrated to the target database is deleted, and the deleted business data is migrated to the target database again in batches.

[0098] It is understandable that when the business migration device detects that the migration status is abnormal, if the formal migration status is abnormal, it will delete all business data that has been migrated to the target database and restart the data migration. Please refer to Figure 5 , Figure 5 Provides an exception retry flow chart.

[0099] Specifically, WRTY formal migration has not been completed: WRTY formal migration has not been completed, that is, WRTY formal migration and the steps before migration have errors. At this time, the data written to the target database by the formal migration needs to be rolled back. WMD rollback mainly rolls back the routing changes in the source database to the original state. DRTY rollback switches to the target database through the database switching operation, and calls the aggregate deletion stored procedure to delete the data written in the target database to complete the rollback. However, this rollback does not require the execution of subsequent logic, and only needs to call the aggregate deletion stored procedure to complete the data deletion.

[0100] In particular, the business migration device can also delete abnormal customers. If a customer still cannot be migrated successfully after retrying, the background provides a function to remove abnormal customers to ensure that other customers in this batch can be migrated normally.

[0101] In a feasible implementation manner, based on the preset migration rule, after the step of acquiring the corresponding business data of the to-be-migrated customers in the migration group, the following steps are included:

[0102] Backing up the business data to obtain backup data;

[0103] It should be noted that the specific migration steps of the business migration equipment include not only the core steps of customer data query, customer data migration to the target system, and migration data verification, but also backup and delete operations on all customer migration data; the backup and delete operations will aggregate the backup and delete operations through database stored procedures, greatly improving the migration efficiency.

[0104] After the formal migration is completed, the step of setting the status field to a valid state, and based on the valid state, post-migrating the unmigrated data in the business data to the target database comprises:

[0105] Acquire target data in the target library;

[0106] It is understandable that the business migration device acquires the data that has been migrated to the target database to obtain the target data.

[0107] The backup data is compared with the target data to obtain a comparison result.

[0108] It should be noted that the business migration device checks the backed-up original data with the migrated target data to obtain a check result. If the check is correct and the migrated business runs for a long time without abnormality, the backup data is deleted.

[0109] In this embodiment, the business migration device provides a complete exception handling mechanism. When an exception occurs in the migration process, the system provides exception retry functions in a single customer dimension and a single batch dimension. The exceptions that occur during the migration process can be quickly handled. At the same time, after the migration is completed, the migration data is checked to avoid the loss of business data.

[0110] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the business migration method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0111] This application also provides a service migration device, please refer to Figure 6 , the service migration device comprises:

[0112] The receiving module 10 is used to receive a migration instruction triggered by a user on a front-end interface, and based on the migration instruction, obtain a migration group selected by the user and a preset migration rule corresponding to the migration group, wherein the migration group includes at least one migration plan, and the migration plan corresponds to at least one customer to be migrated;

[0113] An acquisition module 20, configured to acquire corresponding business data of the customer to be migrated in the migration group based on the preset migration rule, wherein the business data includes core data affecting access of external applications;

[0114] The migration module 30 is used to migrate the business data to the target database in batches, wherein when the core data is being migrated, the external application is prohibited from accessing it.

[0115] Optionally, the migration module includes:

[0116] A submodule is constructed to judge the migration status of each migration plan and obtain a judgment result; if the judgment result is a normal state, an asynchronous thread is constructed for the business data corresponding to each customer to be migrated in the migration plan, and the business data corresponding to the asynchronous thread is migrated in batches to a target library for storing the migrated business data.

[0117] The re-migration sub-module is used to judge the migration status of the post-migration if the status of the formal migration displayed on the front-end interface is normal and the status of the batch migration is abnormal, and to post-migrate the business data corresponding to the abnormal status to the target library again; if the status of the formal migration displayed on the front-end interface is abnormal, the business data that has been migrated to the target library will be deleted, and the deleted business data will be migrated to the target library in batches again.

[0118] Optionally, the construction submodule includes:

[0119] A setting unit is used to pre-migrate the customer data and non-core data before a preset time to the target library; after completing the pre-migration, the status field in the routing table is set to a blocked state to prohibit the external application from accessing, and based on the blocked state, the core data is formally migrated to the target library; after completing the formal migration, the status field is set to a valid state, and based on the valid state, the unmigrated data in the business data is post-migrated to the target library.

[0120] Optionally, the setting unit is further used for:

[0121] Migrate the unmigrated data in the customer data to the target database; and migrate the unmigrated data in the account data to the target database.

[0122] Optionally, the construction submodule includes:

[0123] A backup unit, used to back up the business data to obtain backup data; wherein the construction submodule also includes:

[0124] The checking unit is used to obtain the target data in the target library; check the backup data with the target data to obtain a checking result.

[0125] The service migration device provided by the present application adopts the service migration method in the above embodiment to solve the technical problem of service migration. Compared with the prior art, the beneficial effects of the service migration device provided by the present application are the same as the beneficial effects of the service migration method provided by the above embodiment, and other technical features in the service migration device are the same as the features disclosed in the above embodiment method, which will not be described in detail here.

[0126] The present application provides a business migration device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the business migration method in the above-mentioned embodiment one.

[0127] Reference below Figure 7 , which shows a schematic diagram of the structure of a service migration device suitable for implementing an embodiment of the present application. The service migration device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, tablet computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 7 The service migration device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0128] like Figure 7As shown, the service migration device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the service migration device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the service migration device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a service migration device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.

[0129] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0130] The service migration device provided by the present application adopts the service migration method in the above embodiment to solve the technical problem of service migration. Compared with the prior art, the beneficial effects of the service migration device provided by the present application are the same as the beneficial effects of the service migration method provided by the above embodiment, and other technical features in the service migration device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0131] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0132] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0133] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, wherein the computer-readable program instructions are used to execute the service migration method in the above-mentioned embodiment.

[0134] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0135] The computer-readable storage medium may be included in the service migration device; or may exist independently without being assembled into the service migration device.

[0136] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the business migration device, the business migration device: receives a migration instruction triggered by a user on a front-end interface, and based on the migration instruction, obtains the migration group selected by the user and the preset migration rules corresponding to the migration group, wherein the migration group includes at least one migration plan, and the migration plan corresponds to at least one customer to be migrated; based on the preset migration rules, obtains the corresponding business data of the customer to be migrated in the migration group, wherein the business data includes core data that affects access to external applications; migrates the business data to the target library in batches, wherein, when the core data is being migrated, access by the external application is prohibited.

[0137] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0138] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0139] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0140] The readable storage medium provided in the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned service migration method, and can solve the technical problems of service migration. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the present application are the same as the beneficial effects of the service migration method provided in the above-mentioned embodiment, and will not be described in detail here.

[0141] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned service migration method when executed by a processor.

[0142] The computer program product provided in this application can solve the technical problem of business migration. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as the beneficial effects of the business migration method provided in the above embodiment, which will not be repeated here.

[0143] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A service migration method, characterized in that: The service migration method comprises: Receiving a migration instruction triggered by a user on a front-end interface, and acquiring a migration group selected by the user and a preset migration rule corresponding to the migration group based on the migration instruction, wherein the migration group includes at least one migration plan, and the migration plan corresponds to at least one customer to be migrated; Based on the preset migration rule, obtaining corresponding business data of the customer to be migrated in the migration group, wherein the business data includes core data affecting access of external applications; The business data is migrated to the target database in batches, wherein the external application is prohibited from accessing the core data when the core data is being migrated.

2. The service migration method according to claim 1, characterized in that: The business data includes customer data and account data, the account data includes core data and non-core data, and the step of migrating the business data to the target database in batches includes: Determine the migration status of each migration plan and obtain a determination result; If the judgment result is normal, an asynchronous thread is constructed for the business data corresponding to each of the to-be-migrated customers in the migration plan, and the business data corresponding to the asynchronous thread is migrated in batches to a target library storing the migrated business data.

3. The service migration method according to claim 2, characterized in that: The business data includes customer data and account data, the account data includes core data and non-core data, and the step of migrating the business data corresponding to the asynchronous thread in batches to a target library storing the migrated business data includes: Pre-migrate the customer data and non-core data before a preset time to the target database; After the pre-migration is completed, the status field in the routing table is set to a blocked state to prohibit the external application from accessing it, and based on the blocked state, the core data is formally migrated to the target database; After the formal migration is completed, the status field is set to a valid state, and based on the valid state, the unmigrated data in the business data is post-migrated to the target library.

4. The service migration method according to claim 3, characterized in that: The step of post-migrating the unmigrated data in the business data to the target database comprises: Migrating the unmigrated data in the customer data to the target database; Migrate the unmigrated data in the account data to the target database.

5. The service migration method according to claim 4, characterized in that: The step of migrating the business data to the target database in batches also includes: If the status of the formal migration displayed on the front-end interface is normal and the status of the batch migration is abnormal, the migration status of the post-migration is judged, and the business data corresponding to the abnormal status is post-migrated to the target database again; If the status of the formal migration displayed on the front-end interface is abnormal, the business data that has been migrated to the target database is deleted, and the deleted business data is migrated to the target database again in batches.

6. The service migration method according to claim 3, characterized in that: After the step of acquiring the corresponding business data of the customer to be migrated in the migration group based on the preset migration rule, the following steps are included: Backing up the business data to obtain backup data; After the formal migration is completed, the step of setting the status field to a valid state, and based on the valid state, post-migrating the unmigrated data in the business data to the target database comprises: Acquire target data in the target database; The backup data is compared with the target data to obtain a comparison result.

7. A service migration device, characterized in that: The device comprises: A receiving module, configured to receive a migration instruction triggered by a user on a front-end interface, and based on the migration instruction, obtain a migration group selected by the user and a preset migration rule corresponding to the migration group, wherein the migration group includes at least one migration plan, and the migration plan corresponds to at least one customer to be migrated; An acquisition module, configured to acquire corresponding business data of the customer to be migrated in the migration group based on the preset migration rule, wherein the business data includes core data affecting access of external applications; The migration module is used to migrate the business data to the target database in batches, wherein when the core data is being migrated, the external application is prohibited from accessing it.

8. A service migration device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the service migration method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the service migration method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the service migration method according to any one of claims 1 to 6 are implemented.

Images