Distributed ERP system business domain deployment reconstruction method and system

Abstract

This embodiment provides a distributed ERP system business domain deployment reconstruction method and system, the reconstruction method includes: combing the business functions of each business domain on the ERP system, and the interaction relationship between the data entities of the business functions between different business domains; dividing according to the business functions of each business domain, and obtaining microservices corresponding to each business domain; setting the data flow between each business domain and different business domains according to the business functions of each business domain and the interaction relationship, and setting the functional interface between each business domain and different business domains; performing database adaptation and source code transformation operations; performing independent testing and integration testing on each microservice in the migration platform system, and performing integration testing and performance testing on the data in the migration platform system, and based on the test results, performing trial operation operations, and running in all business departments in stages. The above technical solution can improve the efficiency of ERP system reconstruction.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of information management technology, and more particularly to a method and system for reconfiguring the deployment of a distributed ERP system business domain. Background Art

[0002] With the rapid development of Internet of Things information technology, enterprises have an urgent need for enterprise resource planning systems (ERP). As an enterprise information decision-making and management platform, the ERP system is crucial to the operation of the entire enterprise.

[0003] As the scale of enterprises expands and the complexity of business increases, traditional centralized ERP platforms face challenges in handling large-scale concurrent requests, data processing capabilities, and system scalability. Distributed deployment has become a key means to improve the performance, reliability, and flexibility of ERP platforms. However, when the existing ERP cannot be used or cannot meet the needs of enterprises, it will seriously restrict the office efficiency of enterprises. Summary of the invention

[0004] In view of this, the embodiments of this specification provide a distributed ERP system business domain deployment reconstruction method and system, which can improve the efficiency of ERP system reconstruction.

[0005] The embodiment of this specification provides a distributed ERP system business domain deployment reconstruction method, including:

[0006] Sort out the business functions of each business domain in the ERP system, as well as the interactive relationships between data entities of business functions in different business domains;

[0007] Divide the business domains according to their business functions to obtain microservices corresponding to each business domain.

[0008] According to the business functions of each business domain and the interactive relationship, the data flow direction of each business domain and between different business domains is set, and the functional interface between each business domain and between different business domains is set;

[0009] Perform database adaptation and source code transformation operations to adapt the first database of the ERP system to the second database of the migration platform system, so as to migrate the microservices corresponding to each business domain, as well as the data entities of each microservice, each business domain, and the data flow between different business domains to the migration platform system, and perform security checks on the migration platform system;

[0010] Conduct independent and integration tests on each microservice in the migration platform system, and conduct integration and performance tests on the data in the migration platform system. Based on the test results, perform trial operations and run the system in all business departments in stages.

[0011] Optionally, combing through the business functions of various business domains on the ERP system and the interactive relationships between data entities of business functions between different business domains includes:

[0012] Based on the collected workflow information of each business domain in the ERP system, a process modeling tool is used to generate a business process diagram, wherein the business process diagram includes the functional relationship and data flow direction of each business function of each business domain;

[0013] Analyze the database of the ERP system and identify the data entities in each business domain and the interaction relationship between each data entity by establishing an entity relationship diagram;

[0014] According to the business process diagram, based on the identified business activities, the business functions of each business domain are decomposed into multiple management modules, and according to the calling relationship between each management module, the functional boundary and data entity of each management module and the interaction relationship between each management module are determined;

[0015] According to the interaction relationship between each management module and the interaction relationship between each data entity, a data flow diagram between each management module is constructed, and by identifying the flow path of the data entities of each management module between different management modules, the interaction relationship between the data entities of the business functions between different business domains is determined.

[0016] Optionally, in the step of analyzing the database of the ERP system and identifying data entities in each business domain and the interaction relationship between each data entity by establishing an entity relationship diagram, the reconstruction method further includes:

[0017] A data dictionary corresponding to the data entity is established, wherein the data dictionary includes the definition, data type, value range, and business meaning of the data entity.

[0018] Optionally, setting the data flow direction of each business domain and between different business domains according to the business functions of each business domain and the interaction relationship includes:

[0019] Identify key events in the business functions of each business domain, define the structure and metadata of each key event, and establish a key event processing and routing mechanism to store the data of each business domain in the area corresponding to different routes; select a message queue technology that is compatible with the key events, and use a predefined output transmission protocol format so that the data of each business domain and between different business domains are transmitted in the area corresponding to different routes;

[0020] The setting of each business domain and the functional interface between different business domains includes:

[0021] Standardize the functional interfaces of each business domain and between different business domains, and adopt a version control mechanism to plan the abandonment and migration process of functional interfaces.

[0022] Optionally, performing database adaptation and source code transformation operations to make the first database of the ERP system adapt to the second database of the migration platform system includes:

[0023] Based on the SQL syntax compatibility test, incompatible SQL statements of the first database and the second database are identified, the incompatible SQL statements are rewritten, and the JOIN operation of the first database is adjusted to adapt to the optimizer of the second database;

[0024] Using a static code analysis tool, identifying incompatible code segments between the first database and the second database in the running environment, and performing code reconstruction operations to replace incompatible third-party libraries; and modifying and adjusting system calls and network programming interfaces related to process and thread management of the first database;

[0025] The migrating of the microservices corresponding to each business domain, the data entities of each microservice, each business domain, and the data flows between different business domains to the migration platform system includes:

[0026] Designing a table structure of the second database and partitioning the table structure so as to distribute and store microservices corresponding to each business domain, data entities of each microservice, each business domain, and data flows between different business domains in different areas;

[0027] During the migration process, setting the data extraction strategy and data conversion rules of the second database to handle different data types and format differences, and implementing a rollback mechanism;

[0028] And, setting an index in the table structure to perform a create, modify or delete operation on the data in the second database.

[0029] Optionally, the independent testing and integration testing of each microservice in the migration platform system, as well as the integration testing and performance testing of the data in the migration platform system are performed, and based on the test results, the tests are run in all business departments in stages, including:

[0030] Write test cases for each microservice based on its functions and boundary conditions, including normal process cases and abnormal process cases; identify dependencies between microservices and create simulation objects to replace the dependencies to model various response scenarios; execute the test process to independently test each microservice;

[0031] Build an integrated test environment and perform integration tests on each microservice, including: configure a test server that simulates the production environment, deploy all microservices and dependent components between the microservices on the test server, and configure a network model to simulate the deployment topology of the microservices; design end-to-end test scenarios, including: design test scenarios covering all microservices based on the key business processes and user journeys of each microservice; perform communication tests between the microservices, including: testing synchronous and asynchronous communication modes, verifying load balancing and failover functions, testing security authentication and authorization between services, simulating network delays and disconnections, and verifying the consistency of distributed transactions;

[0032] Based on the dependencies between data entities among various microservices, design data consistency test cases to test the consistency of data entity replication and caching, as well as the data synchronization mechanism; perform data entity migration tests and cross-business domain data synchronization tests; and design automated data verification scripts to verify data integrity;

[0033] Define the key performance indicators and objectives of the performance test; design concurrent operation scripts, simulate high-concurrency scenarios, and monitor the resource usage of the migration platform system; and optimize database query and index strategies based on the resource usage of the migration platform system;

[0034] Select a pilot business department; formulate a trial operation plan and an emergency plan; collect user feedback and system operation data; and conduct a risk assessment based on the trial operation results and the collected user feedback and system operation data.

[0035] Optionally, the reconstruction method further includes:

[0036] When it is determined that the business domain reconstruction in the migration platform system has failed, the business domain reconstruction rollback operation is performed, including: establishing a rollback mechanism, including: defining rollback trigger conditions and formulating rollback operation procedures; configuring quick switching entrances; establishing a data rollback mechanism; rollback drills, including: simulating rollback scenarios in test scenarios, and evaluating the impact of rollback operations on each business domain; optimizing rollback processes, and performing training operations.

[0037] Optionally, the reconstruction method further includes:

[0038] Performing end-to-end encryption operations on data transmission and storage in the ERP system, including: using national encryption algorithms and international general encryption algorithms to build a multi-level encryption system; performing dynamic desensitization operations on sensitive data in the ERP system to process sensitive data; and performing conditional text anonymization operations for privacy enhancement using private attribute randomization, including: identifying private attributes that need to be anonymized and generating random parameters; applying randomization algorithms to change the private attributes, and reconstructing text content according to conditional text semantics;

[0039] Perform identity authentication and access control to determine the permission level of the access user and display the data in the ERP system that is compatible with the permission level;

[0040] A log collection system is set up in the ERP system, including: abnormal behavior detection, including: using a value-penalty-assisted control method without reward or demonstration learning examples and a discrete latent variable enhanced continuous diffusion model to train an anomaly detection model; deploying the anomaly detection model to a working node of the ERP system, detecting abnormal behavior, and generating abnormal behavior alerts and detailed analysis reports.

[0041] Optionally, the reconstruction method further includes:

[0042] Conducting a security audit on the source code of the ERP system, including: classifying and grading the source code of the ERP system and generating multi-dimensional security goals; using a multi-objective combinatorial optimization framework synthesized by large-scale hierarchical populations to perform code scanning and perform audit operations on source codes of different types and levels; generating a security audit report and repair suggestions based on the audit operation results;

[0043] Backing up and restoring the data on the ERP system includes: executing off-site multi-center data backup registration and data backup scheduling based on data priority, wherein the data backup scheduling based on data priority includes: analyzing the correlation and dependency between different data in the ERP system based on dependency-aware priority adjustment technology to determine the priority of each data on the ERP system; establishing a critical time-sensitive network flow model to preferentially allocate time slots for data with higher priority to back up the data with higher priority; and adjusting the priority of the data according to the frequency of data changes and the backup time interval.

[0044] The embodiment of this specification also provides a distributed ERP system business domain deployment and reconstruction system, including:

[0045] The processing unit is adapted to sort out the business functions of each business domain on the ERP system and the interaction relationship between the data entities of the business functions of different business domains; and to divide the business functions of each business domain to obtain microservices corresponding to each business domain;

[0046] A configuration unit adapted to set the data flow direction between each business domain and between different business domains, and to set the functional interface between each business domain and between different business domains according to the business functions of each business domain and the interaction relationship;

[0047] A reconstruction unit, adapted to perform database adaptation and source code transformation operations, so that the first database of the ERP system is adapted to the second database of the migration platform system, so as to migrate the microservices corresponding to each business domain, as well as the data entities of each microservice, each business domain, and the data flows between different business domains to the migration platform system, and perform a security check on the migration platform system;

[0048] A testing unit, adapted to perform independent testing and integration testing on each microservice in the migration platform system, and to perform integration testing and performance testing on the data in the migration platform system, and to generate test results;

[0049] The execution unit is adapted to execute the trial operation based on the test result and to run it in all business departments in stages.

[0050] The distributed ERP system business domain deployment reconstruction method provided in the embodiment of this specification can, on the one hand, sort out the business functions of each business domain on the ERP system and the interactive relationship between the data entities of the business functions of different business domains, perform division operations according to the business functions of each business domain, and obtain microservices corresponding to each business domain, which is conducive to modular development and deployment in subsequent reconstruction and reduces the difficulty of implementation; on the other hand, by determining the data flow direction and configuring the functional interface, it is conducive to the standardization of communication between different business domains and improves the response speed and stability of the subsequent reconstruction process. Afterwards, by performing database adaptation and source code modification operations, the first database of the ERP system can be adapted to the second database of the migration platform system, so that the microservices corresponding to each business domain, as well as the data entities of each microservice, each business domain, and the data flow between different business domains can be migrated to the migration platform system, so as to realize the deployment of the ERP system in different migration platform systems, and improve data security by performing security checks on the migration platform system; then, by performing independent testing and integration testing on each microservice in the migration platform system, as well as integration testing and performance testing on the data in the migration platform system, and based on the test results, performing trial operation operations, and running in all business departments in stages, it is possible to ensure that the reconstruction process is carried out in a stable and orderly manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the embodiments of the present invention 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, the drawings in the following description are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0052] Figure 1 A flowchart of a distributed ERP system business domain deployment and reconstruction method in an embodiment of this specification is shown;

[0053] Figure 2 A flow chart showing a data information sorting process in an embodiment of this specification is shown;

[0054] Figure 3 A flow chart for determining data flow in an embodiment of this specification is shown;

[0055] Figure 4 A schematic diagram of the structure of a distributed ERP system business domain deployment and reconstruction system in an embodiment of this specification is shown. DETAILED DESCRIPTION

[0056] As described in the background art, when the existing ERP system cannot be used or cannot meet the needs of the enterprise, it will seriously restrict the office efficiency of the enterprise. Therefore, it is necessary to reconstruct the ERP system to meet the use needs, but the efficiency of the existing reconstruction solution is too low.

[0057] In order to solve the above technical problems, the embodiments of this specification provide a distributed ERP system business domain deployment reconstruction method. On the one hand, by sorting out the business functions of each business domain on the ERP system and the interactive relationship between the data entities of the business functions of different business domains, it is possible to perform division operations according to the business functions of each business domain to obtain microservices corresponding to each business domain, which is conducive to modular development and deployment in subsequent reconstruction and reduces the difficulty of implementation; on the other hand, by determining the data flow direction and configuring the functional interface, it is conducive to the standardization of communication between different business domains and improves the response speed and stability of the subsequent reconstruction process. Afterwards, by performing database adaptation and source code modification operations, the first database of the ERP system can be adapted to the second database of the migration platform system, so that the microservices corresponding to each business domain, as well as the data entities of each microservice, each business domain, and the data flow between different business domains can be migrated to the migration platform system, so as to realize the deployment of the ERP system in different migration platform systems, and improve data security by performing security checks on the migration platform system; then, by performing independent testing and integration testing on each microservice in the migration platform system, as well as integration testing and performance testing on the data in the migration platform system, and based on the test results, performing trial operation operations, and running in all business departments in stages, it is possible to ensure that the reconstruction process is carried out in a stable and orderly manner.

[0058] In order to enable those skilled in the art to better understand the inventive concept, working principle and advantages of the embodiments of this specification, the voltage regulation scheme in the embodiments of this specification is described in detail below.

[0059] See also Figure 1 Flow chart of a distributed ERP system business domain deployment and reconstruction method in an embodiment of this specification shown in FIG. In some embodiments of this specification, such as Figure 1 As shown, the reconstruction operation can be performed as follows:

[0060] S11, sort out the business functions of each business domain in the ERP system, and the interactive relationship between the data entities of the business functions of different business domains.

[0061] Specifically, there are often multiple business domains in an ERP system, and there are differences and connections between different business domains. Therefore, the business functions of each business domain (such as generating plans, procurement management, and financial settlement functions) can be determined by sorting out the ERP system, and the business process trends of the business functions of each business domain can be analyzed to determine the interactive relationship between the data entities of the business functions of different business domains.

[0062] As an example, for any two business domains, if one of the business domains needs to use data generated by the other business domain, it means that there is a data dependency relationship between the two business domains.

[0063] S12: Divide the business domains according to their business functions to obtain microservices corresponding to the business domains.

[0064] Specifically, different business domains in the ERP system have different functions. By analyzing the business functions of each business domain, each business domain can be split and processed to obtain multiple microservices representing the business domain. In this way, complex business functions can be split into manageable small modules, and the functional boundaries, input and output data of each microservice and the interaction relationship with other microservices can be clarified, which helps to achieve modular development and deployment in subsequent reconstruction.

[0065] S13, according to the business functions of each business domain and the interactive relationship, setting the data flow direction between each business domain and between different business domains, and setting the functional interface between each business domain and between different business domains.

[0066] Specifically, after determining the business functions of each business domain and the interaction between them, the data flow relationship can be set to ensure that data can be transmitted efficiently and securely between the business domains. By setting functional interfaces between each business domain and between different business domains, clear and consistent API interface specifications can be defined, thereby improving the standardization of communications between different business domains and reducing or avoiding situations where data cannot be transmitted or data transmission efficiency is too slow due to interface incompatibility.

[0067] In some embodiments, in the process of setting the data flow, event-driven, message queue and other technologies can also be used to reduce direct coupling and improve the system response speed and stability. S14, perform database adaptation and source code transformation operations to adapt the first database of the ERP system to the second database of the migration platform system, so as to migrate the microservices corresponding to each business domain, the data entities of each microservice, each business domain, and the data flow between different business domains to the migration platform system, and perform a security check on the migration platform system.

[0068] Specifically, after adopting steps S11 to S14 to determine the interaction relationship between different business domains and setting the data flow, the data on the existing ERP system can be migrated to the migration platform system to realize the distributed deployment of the ERP system. In the process of migration, database adaptation and source code transformation operations can be performed to make the first database of the ERP system compatible with the second database of the migration platform system, so that the adaptation of the operating environment can be realized, so that the ERP system migrated to the migration platform system can run smoothly, so that after migrating the microservices corresponding to each business domain, the data entities of each microservice, each business domain, and the data flow between different business domains to the migration platform system, the incompatibility problem can be solved.

[0069] In addition, by conducting security checks on the migration platform system, data security can be improved to ensure that security measures such as data encryption and access control meet design requirements.

[0070] S15, perform independent testing and integration testing on each microservice in the migration platform system, and perform integration testing and performance testing on the data in the migration platform system, and based on the test results, perform trial operation, and run in all business departments in stages.

[0071] Specifically, after transferring data from the ERP system to the migration platform system, the migration platform system can be tested to determine whether the existing migration platform system can correctly and stably run the business functions of each business domain, so as to discover problems in a timely manner and adopt corresponding strategies to solve them.

[0072] After confirming that the test results meet expectations, a trial run can be performed to evaluate the performance of the migration platform system in a real business environment. Based on the trial run results, the system can be run in all business departments in stages to ensure a smooth transition of each business department's business.

[0073] In short, by implementing detailed sorting of business domain functional data, function and data reconstruction planning, information innovation reconstruction (i.e. compatibility testing) and comprehensive testing and phased implementation of business domains, we can ensure the smooth distributed deployment of the ERP platform and achieve efficient operation and sustainable development of the business.

[0074] In some embodiments of the present specification, when it is determined that a distributed ERP system business domain deployment reconstruction plan needs to be executed, it is first necessary to sort out the functional data of the business domain on the ERP system to conduct a comprehensive review of the existing business processes and data models.

[0075] In some embodiments, see Figure 2 A flowchart of a data information sorting process in an embodiment of this specification is shown in FIG. Figure 2 The following combing steps can be performed:

[0076] S21, based on the collected workflow information of each business domain in the ERP system, a business process diagram is generated using a process modeling tool.

[0077] Specifically, by working closely with the business department, we can collect and analyze the workflows of various business domains in the current ERP system and establish business process documents, including but not limited to production planning, procurement relationships and financial settlement. After that, we can use process modeling tools (such as BPMN) to draw business process diagrams.

[0078] In some embodiments, the business process diagram includes the functional relationship and data flow direction of each business function of each business domain. By drawing a business process diagram, the mutual relationship and data flow path of each business link can be intuitively displayed.

[0079] In some embodiments, after the flowchart is drawn, business experts may be organized to conduct a review to improve and modify the business flowchart.

[0080] S22, analyzing the database of the ERP system, and identifying data entities in various business domains and the interaction relationships between various data entities by establishing an entity relationship diagram.

[0081] Specifically, by reviewing the database of the current ERP system, identifying the main tables and views, and analyzing the relationships between the tables, an entity-relationship diagram can be established to determine each data entity (such as customers, orders, and products) from a business perspective, as well as the necessary attributes of each data entity, to determine the relationship between data entities (such as one-to-many or many-to-many relationships), thereby determining the interactive relationships between various data entities.

[0082] S23, according to the business process diagram, based on the identified business activities, the business functions of each business domain are decomposed into multiple management modules, and according to the calling relationship between each management module, the functional boundaries, data entities and interaction relationships between each management module are determined.

[0083] Specifically, since the business process diagram can intuitively show the interrelationships and data flow paths of each business link, the business functions of each business domain can be decomposed into multiple management modules based on the business process diagram and the identification of key business activities (such as production, marketing, finance, etc.) to achieve consistency between module division and business processes. On this basis, the core functions of each management module are clarified, the input and output of each management module are defined, the business rules and constraints of each management module are determined, and the user roles and permission requirements of the module are identified. The functional boundaries and responsibilities of each management module are determined, and then by drawing the call relationship diagram between management modules, the interactive relationship between each management module can be realized by identifying shared data and resources and the communication methods between management modules.

[0084] In some optional examples, the reusability and scalability of the management module can also be evaluated. For example, common functions that may be used by multiple business processes can be identified, the adaptability of the module in different scenarios can be evaluated, the configurability and parameterization of the module can be considered, and the adaptability of the module to future business changes can be evaluated.

[0085] S24, constructing a data flow diagram between various management modules according to the interaction relationship between various management modules and the interaction relationship between various data entities, and determining the interaction relationship between data entities of business functions between different business domains by identifying the flow paths of data entities of various management modules between different management modules.

[0086] Specifically, after determining the interaction between various management modules and the interaction between various data entities, you can choose a DFD tool that is compatible with the reconstruction process, and draw a data flow diagram for the flow of data between various management modules by identifying the main sources and data endpoints of the ERP system. By analyzing the data exchange requirements between management modules, determine the scope and method of data sharing between management modules, and determine the interaction between data entities of business functions between different business domains.

[0087] In some optional embodiments, the data access frequency and access pattern of each management module can also be evaluated by analyzing the high-frequency access data items and low-frequency access data items and the frequency of various data operations (read, write, update, delete) to predict data growth trends and peak load conditions in order to formulate storage strategies.

[0088] And optionally, design a data synchronization mechanism to solve the problem of data anomalies caused by distributed transaction processing.

[0089] In this way, by fully understanding the data structure, functional modules and data flow of the ERP system, a solid foundation is laid for subsequent reconstruction work. This systematic analysis can help the embodiment of the present invention identify potential optimization points and improve the overall efficiency and maintainability of the system.

[0090] In some embodiments of the present specification, in the step of analyzing the database of the ERP system and identifying the data entities in each business domain and the interaction relationships between each data entity by establishing an entity relationship diagram, the reconstruction method also includes: establishing a data dictionary corresponding to the data entity, the data dictionary including the definition, data type, value range, and business meaning of the data entity.

[0091] By establishing a data dictionary, it is possible to query each data entity and further improve the reconstruction efficiency.

[0092] In some embodiments of the present specification, after determining the business functions of each business domain and the interaction relationship between data entities of the business functions between different business domains, the data flow between each business domain and between different business domains can be determined.

[0093] See also Figure 3 A flowchart of determining data flow in an embodiment of this specification is shown in FIG. Figure 3 As shown, the following steps can be performed:

[0094] S31, identifying key events in the business functions of each business domain, defining the structure and metadata of each key event, and establishing a key event processing and routing mechanism to store data of each business domain in areas corresponding to different routes.

[0095] Specifically, different business domains have different business functions, and the key events corresponding to each business function are different (for example, for procurement, the key events can be order creation and inventory changes). In this case, the key event distribution-subscription model can be designed to determine the structure and metadata of each key event, and then consider the order and consistency of key events, and establish a key event processing and routing mechanism, that is, one key event corresponds to one route, and then the data of each business domain can be stored in the area corresponding to different routes.

[0096] For example, each shard can be designed according to the data partitioning dimension (such as time, geographic location, and customer ID), and one shard corresponds to one route to achieve a dynamic balance between the sharding and routing mechanisms.

[0097] S32, selecting a message queue technology that is compatible with the key event, and using a predefined output transmission protocol format, so that data between various business domains and different business domains are transmitted in areas corresponding to different routes.

[0098] Specifically, after establishing the key event processing and routing mechanism, by evaluating the characteristics of different message array technologies (such as throughput, latency and reliability), and considering the scalability requirements and expected data volume of the system, the message queue technology that is compatible with the key event is selected to achieve the persistence and fault tolerance requirements of the message. After that, the serialization / deserialization efficiency of different data formats is evaluated, and the output protocol and format (such as JSON) can be defined, and then the data can be transmitted according to the above rules.

[0099] By adopting the above method and establishing a key event processing and routing mechanism, data can be transmitted in areas corresponding to different routes, so that the data flow direction can be clarified.

[0100] In some embodiments of the present specification, functional interfaces are set for each business domain and between different business domains, including: standardizing the functional interfaces for each business domain and between different business domains, and adopting a version control mechanism to plan the abandonment and migration process of the functional interfaces.

[0101] More specifically, it can include: 1) defining RESTful API design specifications, such as formulating URL naming conventions (such as using plural forms of nouns), standardizing the use of HTTP methods (GET, POST, PUT, DELETE, etc.), designing unified request and response formats, defining standard methods for paging, sorting, and filtering, and standardizing the formats of error codes and error messages; 2) implementing an API version control mechanism, for example, selecting a version control strategy (such as URL path, request header, media type), defining the format and growth rules of the version number, designing a backward compatibility strategy, planning the API deprecation and migration process, and establishing a version document and change log maintenance mechanism.

[0102] In some optional examples, a unified error handling and logging mechanism can also be designed. By defining a standardized error response format, establishing a global exception handling mechanism, and designing a fine-grained error code system, a unified logging framework can be implemented.

[0103] Taking into account the different interfaces between different business domains, an automatic API document generation mechanism can also be established to generate documents.

[0104] In some embodiments of the present specification, a method for obtaining microservices may include: determining the responsibilities and boundaries of each service (ie, determining the granularity and boundaries of microservices) based on business services and the independence and cohesion of business services.

[0105] In some optional examples, you can select a service registry, design service registration and deregistration processes to implement microservice registration, and establish a health detection mechanism to evaluate the performance and scalability of service discovery.

[0106] In some optional examples, considering the role of server health in load balancing, you can choose a load balancing algorithm (such as polling, minimum number of connections) to achieve load balancing. Going further, evaluate the applicable scenarios of synchronous and asynchronous communication to achieve tracking and monitoring of cross-service calls.

[0107] Through these detailed steps, the embodiment of the present invention can systematically plan the function and data reconstruction of the ERP system. This comprehensive design approach can not only improve the scalability and maintainability of the system, but also provide a flexible infrastructure for future business growth and technological evolution. The introduction of event-driven architecture and microservices will make the system more responsive and easy to expand, while the standardized interface design can ensure the consistency and interoperability of various parts of the system.

[0108] By adopting the solution in the above example, it is possible to sort out the data flow and business functions between various businesses, so that the existing ERP system can be transferred to the migration platform system.

[0109] In some embodiments of the present specification, an adaptation operation may be performed to prevent adverse situations such as usage failures from occurring in the migration platform system.

[0110] For example, based on the SQL syntax compatibility test, incompatible SQL statements of the first database and the second database are identified, and the incompatible SQL statements are rewritten, and the JOIN operation of the first database is adjusted to adapt to the optimizer of the second database.

[0111] Specifically, when the database of the migration platform system is selected, an SQL syntax compatibility test can be performed. If incompatible SQL statements are identified, these statements can be modified to achieve adaptation between the first database and the second database and improve compatibility.

[0112] And, the JOIN operation of the first database is adjusted to adapt to the transaction mechanism of the second database according to the transaction processing logic of the second database, so that the optimizer of the second database can be adapted.

[0113] In some embodiments of the present specification, a static code analysis tool is used to identify incompatible code segments between the first database and the second database in the running environment, and to perform code refactoring operations to replace incompatible third-party libraries; and to modify and adjust system calls and network programming interfaces related to the first database process and thread management.

[0114] More specifically, use static code analysis tools to scan the entire code base, identify all codes that directly interact with the operating system, determine the code segments that are incompatible with the second database and the runtime environment, and rewrite the code related to file system operations; and study the differences in APIs and system calls between the first database and the second database, adjust system calls related to process and thread management (for example, modify network programming interfaces, adapt system calls related to memory management and resource allocation, etc.), and improve the compatibility of the first database and the second database.

[0115] In some optional examples, the operating performance of the second database can also be improved by analyzing the hardware architecture information of the second database, optimizing computationally intensive algorithms, adjusting memory access modes, optimizing concurrent processing logic, and other operations.

[0116] In some embodiments of the present specification, the data migration operation may include: designing the table structure of the second database and partitioning the table structure to store the microservices corresponding to each business domain, as well as the data entities of each microservice, each business domain, and the data flow between different business domains in different areas; during the migration process, setting the data extraction strategy and data conversion rules of the second database to handle different data types and format differences, and executing a rollback mechanism; and setting an index in the table structure to perform create, modify or delete operations on the data in the second database.

[0117] In other words, partition control is achieved by adjusting the second database, for example, analyzing and optimizing the table structure design, adjusting the index strategy, including creating, modifying or deleting indexes, and adjusting database parameter configuration, such as the buffer pool size, the number of concurrent connections, etc. After performing the above operations on the second database, a data migration plan can be set based on the second database, for example, formulating a data extraction strategy, designing data conversion rules, handling data type and format differences, and planning the data loading process, so that the second database is more adapted to the needs of the ERP system.

[0118] In some embodiments of this specification, after the adaptation operation is completed, a security compliance check can be performed. For example, a security vulnerability scan is performed, including: selecting a security scanning tool, performing a comprehensive code security audit, and checking common security vulnerabilities, such as SQL injection, XSS, etc., and performing penetration testing to simulate attack scenarios; implementing data encryption and desensitization, including: identifying sensitive data that needs to be encrypted, and selecting an encryption algorithm, implementing data storage and transmission encryption schemes, and implementing a key management mechanism to ensure the safe storage and use of keys, and developing a data desensitization strategy to protect personal privacy information; establishing an access control and identity authentication mechanism, including: implementing a multi-factor authentication mechanism to achieve role-based access control and permission control, and establishing a single sign-on (SSO) system to achieve one-time login and query all business domain information; finally, security auditing and log management can be implemented to achieve centralized log collection and storage, and detect abnormal behavior.

[0119] By implementing the above steps, the ERP system's trust-based reconstruction can be achieved. This process involves not only technical adaptation and optimization, but also ensuring the security and compliance of the system in a localized environment. Database adaptation ensures the smooth migration and efficient processing of data, code transformation enables the system to fully utilize the characteristics of domestic software and hardware, and security compliance checks ensure the safe operation of the system in the new environment. This comprehensive reconstruction approach can help enterprises smoothly complete the transition to a localized IT infrastructure while improving the overall performance and security of the system.

[0120] After migrating the ERP system to the migration platform system, you can perform test tasks to execute the corresponding processing. For ease of understanding, the following example is used to illustrate.

[0121] To perform independent testing on each microservice, you can perform the following steps: write test cases for each microservice based on its functions and boundary conditions, including normal process cases and abnormal process cases; identify the dependencies between microservices, and create simulation objects to replace the dependencies to model various response scenarios; execute the test process to perform independent testing on each microservice.

[0122] Specifically, identify the core functions and boundary conditions of each microservice, design test cases to cover normal processes and abnormal situations, and use the test-driven development (TDD) method to write tests to ensure the independence and repeatability of the tests, consider edge cases and limit value tests, write negative test cases, and verify the error handling mechanism; then, identify the dependencies between microservices, and select a suitable simulation framework (such as Mockito, Sinon.js), create simulation objects to replace external dependencies, to simulate various response scenarios, including success, failure, and timeout, to determine the processing logic of each microservice for the simulated response; then, select a code coverage tool, set coverage targets (such as line coverage, branch coverage), execute tests and generate coverage reports; finally, integrate unit testing into the continuous integration (CI) process, and configure an automated test running environment to achieve independent testing.

[0123] To perform integration testing on each microservice, you can follow these steps: Build an integration testing environment and perform integration testing on each microservice.

[0124] Specifically, configure a test server that simulates the production environment, deploy all microservices and dependent components between the microservices on the test server, and configure a network model to simulate the deployment topology of the microservices; design end-to-end test scenarios, including: based on the key business processes and user journeys of each microservice, design test scenarios covering all the microservices; perform communication tests between the microservices, including: testing synchronous and asynchronous communication modes, verifying load balancing and failover functions, testing security authentication and authorization between services, simulating network delays and disconnections, and verifying the consistency of distributed transactions.

[0125] It should be noted that when performing integration testing, it should be ensured that existing functions are not affected.

[0126] An integration test is performed on the data in the migration platform system, including: designing data consistency test cases based on the dependencies between data entities between various microservices to test the consistency of the data entity replication and caching, as well as the data synchronization mechanism; executing the data entity migration test and cross-business domain data synchronization test; and designing automated data verification scripts to verify the integrity of the data.

[0127] Specifically, you can identify data dependencies across services and design test scenarios to verify data synchronization mechanisms, test the ACID properties of distributed transactions, and verify data version control and conflict resolution mechanisms; and perform data migration tests to test the data conversion logic during the migration process and verify the integrity and consistency of the data after migration; then, test the data flow between different business domains, verify the consistency of cross-domain transactions, test the propagation mechanism of data updates, and verify the permission control of cross-domain data access; finally, develop automated data verification scripts to perform comprehensive data comparison and verification to verify the accuracy of calculated fields and summary data, and check the maintenance of data relationships and constraints.

[0128] Performance testing may include: defining key performance indicators and purposes of performance testing; designing concurrent operation scripts, simulating high-concurrency scenarios, and monitoring resource usage of the migration platform system; and optimizing database query and indexing strategies based on the resource usage of the migration platform system.

[0129] In some examples, it may include: defining key performance indicators (KPIs) and goals, designing test scenarios at different load levels and planning test data sets and test durations, then selecting performance testing tools and setting up monitored system components and indicators, executing high-concurrency scenarios, simulating user access from different geographical locations through gradually increasing load patterns to test the system's performance under peak load; finally, tracking CPU, memory, disk I / O, and network usage, monitoring database performance and connection pool status, as well as the response time and throughput of microservices, identifying operations and services with longer response times, optimizing database queries and indexes, adjusting cache strategies and configurations, and optimizing code and algorithm efficiency.

[0130] The trial operation includes: selecting a pilot business department; formulating a trial operation plan and an emergency plan; collecting user feedback and system operation data; and conducting a risk assessment based on the trial operation results and the collected user feedback and system operation data.

[0131] It will be run in all business departments in stages, including: formulating a comprehensive deployment plan, including: adjusting the deployment strategy based on the trial operation experience, and formulating a detailed deployment schedule and milestones, and planning the required hardware and network resources; sorting the implementation order by business importance, including: evaluating the criticality of each business domain, and considering the dependencies between business domains, as well as evaluating the readiness and acceptance of each department, balancing risks and benefits to set priorities; gradually expanding the scope of deployment, including: deploying business domains or departments one by one as planned, and conducting stability assessments after each deployment, as well as resolving problems that arise during the deployment process, and collecting and analyzing feedback at each stage to ensure a smooth transition from the old to the new system; continuously monitoring and optimizing system performance, including: establishing a comprehensive system monitoring mechanism, and regularly analyzing performance data and user feedback, and implementing a continuous performance tuning plan.

[0132] Through these detailed steps, the embodiment of the present invention can systematically conduct comprehensive testing and phased implementation of the ERP system. This process not only ensures the technical quality of the system, but also verifies the implementation risks through trial operation and phased deployment. Unit testing and integration testing ensure the functional correctness of each component and the overall system, data integration testing ensures the consistency and integrity of the data, and performance testing verifies the performance of the system under actual load. The trial operation phase provides valuable actual operation experience and prepares for full deployment. Finally, through phased implementation and continuous optimization, the embodiment of the present invention can ensure that the ERP system is smoothly and efficiently put into use and can continue to meet business needs.

[0133] In actual applications, if the reconstructed business domain is affected by uncontrollable factors such as poor hardware performance, insufficient network bandwidth, server overload, etc., resulting in the reconstructed business domain failing to achieve the expected results, you can roll back to the state before the reconstruction by simply configuring the entry.

[0134] Specifically, when it is determined that the business domain reconstruction in the migration platform system fails, a business domain reconstruction rollback operation is performed.

[0135] In some embodiments, the rollback operation includes: establishing a rollback mechanism, including: defining rollback trigger conditions and formulating a rollback operation process. For example, identifying key performance indicators (KPIs) and system health metrics, and setting thresholds such as system response time, error rate, transaction success rate, and standards for business continuity interruption as rollback trigger conditions.

[0136] Configure a fast switching entry, including: developing a configuration management system to support fast switching function switches, and a distributed configuration center to ensure the real-time nature of configuration changes, as well as dynamically configure the routing layer to achieve fast traffic switching.

[0137] Establish a data rollback mechanism, including: designing an incremental data backup strategy and adopting the data snapshot function to support data recovery at a specific point in time, setting up a data version control system to track data change history to implement a transaction log replay mechanism, implement fine-grained data rollback, and design a cross-service data consistency rollback strategy;

[0138] Rollback drills include: simulating rollback scenarios in test scenarios and evaluating the impact of rollback operations on various business domains; optimizing rollback processes and performing training operations.

[0139] Specifically, simulate the rollback scenario in the test environment, build a test environment similar to the production environment, and design multiple rollback scenarios to cover different trigger conditions. Then simulate various system failures and performance issues and execute an end-to-end rollback process. Next, measure the execution time of the rollback operation, and determine the time required for the system to return to a usable state, the risk of data loss during the rollback process, calculate the potential financial losses during the rollback process, and evaluate the impact of the rollback on customer experience and company reputation. Finally, analyze the bottlenecks and problems found in the rollback drill, use rollback scripts and automation tools to improve data rollback strategies and reduce the risk of data loss.

[0140] In some optional examples, the rollback operation may also include: formulating a rollback operation process and a responsibility division mechanism. For example, establishing an evaluation and approval process for rollback decisions, defining the steps and checkpoints for rollback operations, assigning responsibilities and permissions to each role in the rollback process, formulating a system verification and business confirmation process after the rollback, establishing a real-time communication mechanism for the rollback process, and formulating a problem analysis and improvement plan after the rollback.

[0141] Train relevant personnel to be familiar with rollback operations.

[0142] Perform monitoring and early warning operations, including: establishing system performance monitoring indicators, such as defining key performance indicators (KPIs) and service level agreements (SLAs), and implementing a comprehensive system health check mechanism, as well as monitoring the response time and throughput of each microservice, tracking database performance and query execution time in real time, and monitoring network latency and bandwidth usage; setting self-alert thresholds, such as setting performance benchmarks based on historical data and business needs, configuring dynamic thresholds, implementing multi-level early warning mechanisms, including warning, serious and emergency levels, adapting to business peak and valley changes, and setting composite early warning rules, integrating multiple indicators, establishing an early warning upgrade mechanism, and ensuring timely processing; implementing real-time log analysis, such as centrally collecting and storing logs of all services, and processing and analyzing log streams in real time, using machine learning algorithms to identify abnormal log patterns; and establishing a rapid response mechanism.

[0143] Through these detailed steps, the embodiment of the present invention can establish a comprehensive and effective business domain reconstruction fallback mechanism. This mechanism not only includes the rapid switching and data rollback capabilities at the technical level, but also covers the processes, division of responsibilities and training at the organizational level. Through regular rollback drills, the embodiment of the present invention can continuously optimize the rollback process and improve the team's response capabilities. At the same time, a powerful monitoring and early warning system can help the embodiment of the present invention detect problems early and make rollback decisions quickly when necessary. Such preparation can greatly reduce the risks in the reconstruction process, ensuring that even in the event of unexpected situations, the impact on the business can be minimized, ensuring the stability and reliability of the system.

[0144] In some embodiments, when performing data migration or data storage, end-to-end encryption operations may also be performed on data transmission and storage in the ERP system.

[0145] In this step, the embodiments of this specification will implement comprehensive end-to-end encryption for data transmission and storage in the ERP system. This means that the data is encrypted throughout its entire life cycle from generation to use. The specific implementation includes: using national encryption algorithms and international general encryption algorithms to build a multi-level encryption system; performing dynamic desensitization operations on sensitive data in the ERP system to process sensitive data; and using private attribute randomization to perform privacy-enhanced conditional text anonymization operations, including: identifying private attributes that need to be anonymized and generating random parameters; applying randomization algorithms to change the private attributes, and reconstructing the text content according to the conditional text semantics.

[0146] In one embodiment, the TLS / SSL protocol is used at the data transmission layer to ensure the security of data during network transmission, and a strong encryption algorithm, such as AES-256, is used for sensitive information stored in the database. An encryption key management system is implemented to rotate keys regularly and ensure the secure storage of keys.

[0147] Specifically, in order to meet national information security standards and requirements, the embodiments of this specification will adopt a hybrid encryption scheme that combines national encryption algorithms with international general encryption algorithms, such as using the SM2 algorithm for asymmetric encryption for key exchange and digital signatures, and using the SM4 algorithm for symmetric encryption to protect the confidentiality of large amounts of data; another example is using the SM3 algorithm as a hash function to ensure data integrity; another example is combining international algorithms such as AES and RSA to build a multi-level encryption system that takes into account system performance and compatibility while ensuring security.

[0148] Then, implement dynamic desensitization of sensitive data. Dynamic desensitization is a key technology for protecting sensitive data. It can process sensitive information in real time when the data is accessed, including: establishing a sensitive data classification system to clearly define the types of data that need to be desensitized, such as personal identity information, financial data, etc.; developing a dynamic desensitization rule engine that can dynamically determine the desensitization strategy based on user roles, access context and data types; implementing a variety of desensitization technologies, including but not limited to: data masking, data replacement, scoping, tokenization, etc.; implementing desensitization logic at the database query layer to ensure that sensitive data has been desensitized before being returned to the application layer; and establishing a desensitization audit log to record all desensitization operations for subsequent security audits and compliance checks.

[0149] Finally, we use private attribute randomization to achieve privacy-enhanced conditional text anonymization, where this technology can protect personal privacy to the greatest extent while retaining the value of data usage:

[0150] Specifically, it includes: analyzing text data in the ERP system, identifying attributes that may involve personal privacy, such as name, ID, address, etc., and then establishing a private attribute dictionary and rule base to support automatic identification and marking of information that needs to be anonymized, and using natural language processing technology to identify private information implicit in the context; then, generating unique randomized parameters for each identified private attribute, and using a cryptographically secure random number generator to ensure the unpredictability of the parameters; finally,

[0151] Using a series of randomization algorithms, such as permutation, additive homomorphic encryption, local differential privacy, etc., according to the data type and usage scenario, apply the selected algorithm, use the generated random parameters to transform the private attributes, and combine it with the analysis of the semantic structure of the text to identify key semantic elements and relationships. Use natural language generation technology to reconstruct the text containing anonymized private attributes to ensure that the reconstructed text remains consistent and natural in terms of grammar and semantics.

[0152] And optionally, develop an anonymization quality assessment model to evaluate from two dimensions: privacy protection and information retention. For example, use differential privacy theory to verify the privacy protection strength of anonymized data, and perform information entropy analysis to ensure that the loss of key information during the anonymization process is within an acceptable range.

[0153] Through the above detailed steps, the embodiment of the present invention can achieve comprehensive and in-depth data encryption and privacy protection in the ERP system. This not only meets the increasingly stringent data protection regulations, but also provides enterprises with strong data security protection while maintaining the availability and value of data.

[0154] And, identity authentication and access control are performed to determine the permission level of the access user so as to display the data in the ERP system that is compatible with the permission level.

[0155] And, a log collection system is set in the ERP system, including: abnormal behavior detection, including: using a value-penalty-assisted control method without reward or demonstration learning examples and a discrete latent variable enhanced continuous diffusion model to train an anomaly detection model; deploying the anomaly detection model to a working node of the ERP system, detecting abnormal behavior, and generating abnormal behavior alerts and detailed analysis reports.

[0156] Specifically, AI-assisted abnormal behavior detection can greatly improve the security and reliability of the system. This process involves multiple complex steps, each of which incorporates advanced machine learning technology.

[0157] Specifically, a value-penalty-assisted control method without reward or demonstration learning examples is adopted. This step introduces a novel learning method that does not rely on traditional reward mechanisms or large amounts of labeled data. Among them, the control method includes: establishing a behavioral baseline model: analyzing historical data to establish a baseline model of normal user behavior and system operation; designing a value function: defining a value function to evaluate the "normality" of behavior; adopting an implementation penalty mechanism: imposing penalties on operations that deviate from normal behavior patterns, which are reflected in the score of the value function, and adaptive learning: the system continuously adjusts and optimizes the value function through continuous observation and learning, and improves its ability to identify new abnormal behaviors; unsupervised anomaly detection: using this method, the system can autonomously learn to identify potential abnormal behaviors without explicitly labeled abnormal samples, so that this function does not rely on external rewards, but is based on the system's internal laws and predefined security policies.

[0158] In addition, discrete latent variables are introduced to enhance the continuous diffusion model to better capture the temporal characteristics and potential patterns of behavioral data. The diffusion model includes: constructing a continuous diffusion model: based on the temporal data of user behavior and system logs, a diffusion model that can simulate the data generation process is constructed; introducing discrete latent variables: introducing discrete latent variables in the continuous diffusion model to capture discrete state transitions in behavioral patterns; designing an encoder-decoder structure: realizing a network structure that can map the observed behavioral data to the latent space and reconstruct the behavioral data from the latent space; optimizing the training process: using the variational inference method to optimize the model parameters so that it can accurately reconstruct normal behavior and be sensitive to abnormal behavior; anomaly detection strategy: using the trained model to detect anomalies by comparing the differences between the actual observed behavior and the behavior generated by the model.

[0159] Next, the methods developed in the first two steps are combined to train a powerful anomaly detection model, including: data preprocessing: cleaning, standardizing and feature extraction of collected user behavior data and system logs; model architecture design: combining value-penalty-assisted control and discrete latent variable enhanced diffusion model to design an end-to-end anomaly detection network; phased training: first use a large amount of unlabeled data for self-supervised learning, and then use a small amount of labeled data for fine-tuning; cross-validation: use techniques such as k-fold cross-validation to ensure the generalization ability of the model; model interpretability: introduce attention mechanism and explainable AI technology to make the decision-making process of the model more transparent. Continuous learning: design an online learning mechanism so that the model can continuously learn from new data and adapt to the changing environment.

[0160] Finally, the anomaly detection model is deployed to the production environment to achieve real-time abnormal behavior detection, including: streaming data processing: establishing a real-time data pipeline to efficiently process continuously generated system logs and user behavior data; real-time feature extraction: developing an efficient feature extraction algorithm that can extract key features in real time from the data stream; model reasoning optimization: using model quantization, pruning and other technologies to optimize the model and achieve low-latency real-time reasoning; multi-scale analysis: performing short-term (seconds), medium-term (minutes) and long-term (hours / days) behavior analysis simultaneously to comprehensively capture different types of anomalies; contextual awareness: considering contextual information such as user roles, time, and location to improve detection accuracy; adaptive threshold: dynamically adjusting the anomaly judgment threshold based on system load, time and other factors.

[0161] Abnormal behavior alerts and detailed analysis reports can then be generated to transform detection results into actionable information, enabling security teams to respond quickly.

[0162] Among them, alerts can be graded according to the severity and potential impact of the anomalies to ensure that important alerts are handled first; and detected anomalies can be associated with historical events and known threat intelligence to provide a more comprehensive threat assessment; you can also: develop intuitive dashboards to display anomaly detection results, trend analysis and the overall security status of the system, and design templates to automatically generate detailed reports containing anomaly details, impact assessments and recommended actions; finally, based on the type and severity of the detected anomalies, provide preliminary response recommendations and mitigation measures to continuously optimize the model and report generation process.

[0163] Through this series of steps, the ERP system will have advanced AI-assisted abnormal behavior detection capabilities, which can timely discover and respond to various potential security threats, greatly improving the overall security and reliability of the system. This method can not only detect known attack patterns, but also identify new and unseen abnormal behaviors, providing enterprises with all-round security protection.

[0164] In some embodiments of the present specification, during the reconstruction process of the ERP system, source code security audit is a key step to ensure system security, so the reconstruction method may also include: performing a security audit on the source code of the ERP system.

[0165] Specifically, the method includes: classifying and grading the source code of the ERP system and generating multi-dimensional security goals; using a multi-objective combinatorial optimization framework synthesized by large-scale hierarchical populations to perform code scanning and audit operations on source codes of different types and levels; and generating a security audit report and repair suggestions based on the audit operation results.

[0166] In an optional example, the efficiency and effectiveness of auditing can be significantly improved by adopting an innovative multi-objective combinatorial optimization framework of large-scale hierarchical population synthesis.

[0167] Among them, the multi-objective combinatorial optimization framework of large-scale hierarchical population synthesis allows efficient security audits in complex code bases, including: framework design: building a multi-level optimization framework, each layer represents a code audit strategy at a different level of abstraction; population initialization: creating an initial population for each layer, each individual represents a possible audit strategy combination; fitness function definition: designing a multi-objective fitness function, considering factors such as audit coverage, resource consumption, and vulnerability discovery rate; evolutionary algorithm implementation: using an improved genetic algorithm or particle swarm optimization algorithm to exchange and optimize information between layers; balancing exploration and utilization: in the optimization process, balancing global search (exploring new strategies) and local search (improving existing strategies); parallel computing: using distributed computing technology to accelerate the evaluation and evolution process of large-scale populations.

[0168] Furthermore, in order to conduct audits more targeted, the source code can also be systematically classified, which can be divided based on multiple dimensions: 1) Functional module division: divide the code into different modules according to its function, such as user authentication, data processing, network communication, etc. 2) Risk level division: assign a risk level to each module based on the importance, complexity and potential security impact of the code. 3) Technology stack classification: classify the code according to the programming language, framework and library used so that specific audit rules can be applied. 4) Update frequency analysis: identify "hot" code areas that are frequently changed and may require more frequent audits. 5) Dependency graph construction: analyze and visualize the dependencies between code modules to understand potential security propagation paths. 6) Historical vulnerability association: associate code modules with the types of vulnerabilities discovered historically to identify high-risk areas.

[0169] Finally, multi-dimensional security goals are generated to comprehensively ensure system security.

[0170] For example, vulnerability type coverage: ensure that the audit covers common vulnerability types such as the OWASP Top 10, as well as security risks specific to ERP systems.

[0171] Compliance requirements: Define compliance goals based on industry standards and regulatory requirements (such as GDPR, PCI DSS, etc.).

[0172] Performance impact assessment: Consider the potential impact of security measures on system performance and balance security and efficiency.

[0173] Maintainability goal: Ensure that security practices do not excessively increase code complexity and affect long-term maintainability.

[0174] Security boundary integrity: Evaluate and strengthen the boundaries between different security domains to prevent unauthorized access.

[0175] Encryption standards: Define and enforce appropriate encryption standards to protect sensitive data.

[0176] Then, we use the multi-objective combination optimization framework of large-scale hierarchical population synthesis to generate audit strategies. This includes: generating optimized audit strategies for different code modules, and reasonably allocating audit resources based on risk assessment results, focusing on high-risk areas, and selecting the most suitable static and dynamic analysis tools for different types of codes, so as to generate customized code audit rules based on the special needs of the ERP system, and dynamically adjusting the depth and breadth of the audit according to the complexity and risk level of the code, so as to formulate the optimal audit schedule and balance the audit frequency and development progress.

[0177] Finally, a comprehensive report is generated and practical suggestions for improvement are provided. For example, vulnerability classification and summary: classify and summarize the security issues found, highlighting key risks; severity assessment: assign severity levels to each problem found to help the team prioritize key issues; root cause analysis: in-depth analysis of the root causes of security issues to avoid similar problems from happening again; repair suggestions: provide specific repair suggestions for each security issue, including code examples and best practices; trend analysis: compare the results of previous audits to identify trends in improvement or deterioration of security conditions; visualization: use charts and visualization tools to intuitively display audit results and security status; knowledge base construction: organize audit findings and repair experience into a knowledge base to serve future development and audit work.

[0178] In some optional examples, an audit process that combines automated code scanning and manual review can also be performed, that is, combining automated tools and manual expertise to achieve efficient and comprehensive code audits to reduce false positives.

[0179] By implementing this series of steps, the source code security audit process of the ERP system will become more systematic, intelligent and efficient. This approach can not only fully identify and repair existing security vulnerabilities, but also continuously improve development practices and improve system security from the source. At the same time, by optimizing resource allocation and policy generation, it can achieve the maximum security benefits within limited time and resources, providing strong protection for the reliable operation of the ERP system.

[0180] In some embodiments of this specification, in order to further improve the security of data, the data on the ERP system can also be backed up and restored.

[0181] Specifically, it includes: executing off-site multi-center data backup registration and data backup scheduling based on data priority, wherein data backup scheduling based on data priority includes: based on dependency-aware priority adjustment technology, analyzing the correlation and dependency between different data in the ERP system to determine the priority of each data on the ERP system; establishing a critical time-sensitive network flow model to preferentially allocate time slots for higher priority data to back up higher priority data; and adjusting the priority of data according to the frequency of data changes and the backup time interval.

[0182] In an optional example, in an ERP system, an efficient and reliable data backup strategy is essential to ensure business continuity and data security. By implementing priority-based data backup scheduling, the protection of critical data can be maximized within a limited backup window. And by using dependency-aware priority adjustment technology, the backup priority can be dynamically adjusted based on the complex dependencies between data. Among them, it includes: dependency graph construction: building a comprehensive data dependency graph to reflect the association between different data sets in the ERP system; priority calculation model: designing a mathematical model to calculate the initial priority of data based on the depth and breadth of dependencies; cascade impact analysis: evaluating the cascading impact that the loss of a certain data set may have on the entire system; dynamic weight allocation: dynamically adjusting the weights of different data sets based on the real-time status of the business process; feedback mechanism: establishing a feedback loop to continuously optimize the priority calculation based on the actual backup performance and recovery test results; and, anomaly detection: implementing anomaly detection mechanism to quickly identify and respond to sudden changes in data dependencies.

[0183] Next, a mixed criticality TSN (time-sensitive network) flow model is established, and the concept of time-sensitive network is applied to data backup to better handle data flows of different priorities. That is, appropriate time slots are allocated to different types of data flows to ensure timely backup of high-priority data, and necessary network bandwidth is reserved for critical data flows to prevent congestion during the backup process.

[0184] Finally, dynamically adjust the priority of backup tasks to implement a system that can dynamically adjust the priority of backup tasks according to real-time conditions, including: real-time monitoring system: deploy monitoring tools to track key indicators such as data change rate and system load in real time; priority scoring mechanism: establish a scoring system that comprehensively considers factors such as data importance, change frequency, and last backup time; dynamic queue management: implement a queue management system that can dynamically reschedule backup tasks according to real-time priority; resource competition processing: implement an intelligent decision-making mechanism when multiple high-priority tasks compete for resources; emergency insertion mechanism: allow emergency backup tasks to be quickly inserted into the current backup queue; priority adjustment audit: record all priority adjustment operations for subsequent analysis and optimization.

[0185] And optionally, optimize the backup window to ensure timely backup of critical data, including:

[0186] Effectively manage the backup window to maximize backup efficiency, for example, backup window analysis: analyze business operation patterns to identify the best backup time window; incremental backup strategy: implement intelligent incremental backup strategy to reduce the time and resources required for each backup; parallel backup technology: use parallel processing technology to simultaneously back up multiple non-conflicting data sets.

[0187] Compression and deduplication: Apply efficient data compression and deduplication technology to reduce the amount of backup data.

[0188] Backup task splitting: Split large backup tasks into multiple small tasks to improve overall backup flexibility.

[0189] Adaptive Scheduling: Dynamically adjust the execution time of backup tasks based on real-time system load and network conditions.

[0190] And, monitor and adjust backup performance to ensure that the recovery point objective (RPO) is met, including: displaying the current RPO status of each key data set and tracking key performance indicators such as backup completion time, data transfer rate, etc.; then, promptly notifying the administrator when the RPO is about to be violated, and analyzing the root cause of backup failure or delay; finally, based on historical data and growth trends, conduct forward-looking backup capacity planning, and arrange regular recovery tests to verify the effectiveness of backups and the achievability of recovery time objectives (RTO) to establish a continuous improvement process and regularly review and optimize the entire backup strategy.

[0191] By implementing this series of steps, the data backup process of the ERP system will become more intelligent, efficient and reliable. This priority-based data backup scheduling method can not only ensure that critical business data is protected in a timely and reliable manner, but also optimize resource usage and reduce the impact on daily business operations. By utilizing innovative technologies such as dependency-aware priority adjustment and TSN flow model, the system can better cope with complex data dependencies and time-sensitive requirements, providing enterprises with a powerful and flexible data protection solution.

[0192] In summary, the embodiments of this specification provide a systematic method for reconstructing the business domain of distributed deployment of an ERP system. Through a series of standardized steps, the whole process from business combing to system reconstruction is efficiently completed, ensuring the smooth implementation of the distributed transformation of the ERP system. This method not only improves the efficiency of system reconstruction, but also enhances the stability and maintainability of the system, providing a solid foundation for the digital transformation of enterprises.

[0193] The embodiment of this specification also provides a system corresponding to the distributed ERP system business domain deployment reconstruction method, such as Figure 4 The structure diagram of a distributed ERP system business domain deployment and reconstruction system in an embodiment of the present invention is shown in FIG. Figure 4 As shown, the distributed ERP system business domain deployment reconstruction system 100 may include:

[0194] The processing unit 110 is adapted to sort out the business functions of each business domain on the ERP system and the interaction relationship between the data entities of the business functions of different business domains; and to divide the business functions of each business domain to obtain microservices corresponding to each business domain;

[0195] The configuration unit 120 is adapted to set the data flow direction between each business domain and between different business domains, and to set the functional interface between each business domain and between different business domains according to the business functions of each business domain and the interaction relationship;

[0196] The reconstruction unit 130 is adapted to perform database adaptation and source code transformation operations, so that the first database of the ERP system is adapted to the second database of the migration platform system, so as to migrate the microservices corresponding to each business domain, as well as the data entities of each microservice, each business domain, and the data flow between different business domains to the migration platform system, and perform a security check on the migration platform system;

[0197] The testing unit 140 is adapted to perform independent testing and integration testing on each microservice in the migration platform system, and to perform integration testing and performance testing on the data in the migration platform system, and generate test results;

[0198] The execution unit 150 is adapted to execute a trial operation based on the test result and to run the operation in all business departments in stages.

[0199] The specific working processes and principles of the processing unit 110 , the configuration unit 120 , the reconstruction unit 130 , the testing unit 140 and the execution unit 150 may refer to the relevant description of the aforementioned examples.

[0200] It is understandable that the division of the above units is only a division of logical functions, and in actual implementation, they can be fully or partially integrated into one physical entity, or physically separated. In addition, the above units can be implemented in the form of a processor calling software.

[0201] The present invention also provides a computer system suitable for implementing a distributed ERP system business domain deployment reconstruction method, wherein the computer system includes a central processing unit (CPU), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) or a program loaded from a storage part to a random access memory (RAM), such as executing the method described in the above embodiment. Various programs and data required for system operation are also stored in the RAM. The CPU, ROM, and RAM are connected to each other via a bus. The input / output (I / O) interface is also connected to the bus.

[0202] The following components are connected to the I / O interface: an input part including a keyboard, a mouse, etc.; an output part including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage part including a hard disk, etc.; and a communication part including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication part performs communication processing via a network such as the Internet. The drive 310 is also connected to the I / O interface as needed. Removable media, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memories, etc., are installed on the drive as needed so that the computer program read therefrom can be installed into the storage part as needed.

[0203] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program 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 part, and / or installed from a removable medium. When the computer program is executed by a central processing unit (CPU), various functions defined in the system of the present application are executed.

[0204] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, 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), a 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.

[0205] In the present application, a 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, apparatus, or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable computer program. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0206] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, 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 box can also occur in a different order from the order marked in the accompanying drawings. For example, two 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 box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart 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.

[0207] The units involved in the embodiments of the present invention may be implemented by software or hardware, and the units described may also be arranged in a processor. The names of these units do not, in some cases, limit the units themselves.

[0208] According to one aspect of the present application, a computer program product or a computer program is provided, the computer program product or the computer program comprising computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the methods provided in the above-mentioned various optional implementations.

[0209] As another aspect, the present application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by an electronic device, the electronic device implements the method described in the above embodiment.

[0210] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0211] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software, or by combining software with necessary hardware. Therefore, the technical solution according to the implementation method of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation method of the present application.

[0212] Although the embodiments of this specification are disclosed as above, the present invention is not limited thereto. Any person skilled in the art can make various changes and modifications without departing from the spirit and scope of the present invention, so the protection scope of the present invention shall be subject to the scope defined by the claims.

Claims

1. A distributed ERP system business domain deployment reconstruction method, characterized in that: include: Sort out the business functions of each business domain in the ERP system, as well as the interactive relationships between data entities of business functions in different business domains; Divide the business domains according to their business functions to obtain microservices corresponding to each business domain. According to the business functions of each business domain and the interactive relationship, the data flow direction of each business domain and between different business domains is set, and the functional interface between each business domain and between different business domains is set; Perform database adaptation and source code transformation operations to adapt the first database of the ERP system to the second database of the migration platform system, so as to migrate the microservices corresponding to each business domain, as well as the data entities of each microservice, each business domain, and the data flow between different business domains to the migration platform system, and perform security checks on the migration platform system; Conduct independent and integration tests on each microservice in the migration platform system, as well as integration and performance tests on the data in the migration platform system, and based on the test results, perform trial operations and run the system in all business departments in stages; The process of combing the business functions of each business domain on the ERP system and the interactive relationships between data entities of business functions between different business domains includes: Based on the collected workflow information of each business domain in the ERP system, a process modeling tool is used to generate a business process diagram, wherein the business process diagram includes the functional relationship and data flow direction of each business function of each business domain; Analyze the database of the ERP system and identify the data entities in each business domain and the interaction relationship between each data entity by establishing an entity relationship diagram; According to the business process diagram, based on the identified business activities, the business functions of each business domain are decomposed into multiple management modules, and according to the calling relationship between each management module, the functional boundary and data entity of each management module and the interaction relationship between each management module are determined; According to the interaction relationship between various management modules and the interaction relationship between various data entities, a data flow diagram between various management modules is constructed, and by identifying the flow path of data entities of various management modules between different management modules, the interaction relationship between data entities of business functions in different business domains is determined; The setting of the data flow between each business domain and between different business domains according to the business functions of each business domain and the interaction relationship includes: Identify key events in the business functions of each business domain, define the structure and metadata of each key event, and establish a key event processing and routing mechanism to store the data of each business domain in the area corresponding to different routes; select a message queue technology that is compatible with the key events, and use a predefined output transmission protocol format so that the data of each business domain and between different business domains are transmitted in the area corresponding to different routes; The setting of each business domain and the functional interface between different business domains includes: Standardize the functional interfaces of each business domain and between different business domains, and adopt a version control mechanism to plan the abandonment and migration process of functional interfaces; The performing of database adaptation and source code transformation operations so that the first database of the ERP system is adapted to the second database of the migration platform system includes: Based on the SQL syntax compatibility test, incompatible SQL statements of the first database and the second database are identified, the incompatible SQL statements are rewritten, and the JOIN operation of the first database is adjusted to adapt to the optimizer of the second database; Using a static code analysis tool, identifying incompatible code segments between the first database and the second database in the running environment, and performing code reconstruction operations to replace incompatible third-party libraries; and modifying and adjusting system calls and network programming interfaces related to process and thread management of the first database; The migrating of the microservices corresponding to each business domain, the data entities of each microservice, each business domain, and the data flows between different business domains to the migration platform system includes: Designing a table structure of the second database and partitioning the table structure so as to distribute and store microservices corresponding to each business domain, data entities of each microservice, each business domain, and data flows between different business domains in different areas; During the migration process, setting the data extraction strategy and data conversion rules of the second database to handle different data types and format differences, and implementing a rollback mechanism; And, setting an index in the table structure to perform a create, modify or delete operation on the data in the second database.

2. The reconstruction method according to claim 1, characterized in that: In the step of analyzing the database of the ERP system and identifying the data entities in each business domain and the interaction relationship between each data entity by establishing an entity relationship diagram, the reconstruction method further includes: A data dictionary corresponding to the data entity is established, wherein the data dictionary includes the definition, data type, value range, and business meaning of the data entity.

3. The reconstruction method according to claim 1, characterized in that: The above mentioned independent and integrated testing of each microservice in the migration platform system, as well as integration and performance testing of the data in the migration platform system, are carried out in stages in all business departments based on the test results, including: Write test cases for each microservice based on its functions and boundary conditions, including normal process cases and abnormal process cases; identify dependencies between microservices and create simulation objects to replace the dependencies to model various response scenarios; execute the test process to independently test each microservice; Build an integrated test environment and perform integration tests on each microservice, including: configure a test server that simulates the production environment, deploy all microservices and dependent components between the microservices on the test server, and configure a network model to simulate the deployment topology of the microservices; design end-to-end test scenarios, including: design test scenarios covering all microservices based on the key business processes and user journeys of each microservice; perform communication tests between the microservices, including: testing synchronous and asynchronous communication modes, verifying load balancing and failover functions, testing security authentication and authorization between services, simulating network delays and disconnections, and verifying the consistency of distributed transactions; Based on the dependencies between data entities among various microservices, design data consistency test cases to test the consistency of data entity replication and caching, as well as the data synchronization mechanism; perform data entity migration tests and cross-business domain data synchronization tests; and design automated data verification scripts to verify data integrity; Define the key performance indicators and objectives of the performance test; design concurrent operation scripts, simulate high-concurrency scenarios, and monitor the resource usage of the migration platform system; and optimize database query and index strategies based on the resource usage of the migration platform system; Select a pilot business department; formulate a trial operation plan and an emergency plan; collect user feedback and system operation data; and conduct a risk assessment based on the trial operation results and the collected user feedback and system operation data.

4. The reconstruction method according to claim 1, characterized in that: Also includes: When it is determined that the business domain reconstruction in the migration platform system has failed, the business domain reconstruction rollback operation is performed, including: establishing a rollback mechanism, including: defining rollback trigger conditions and formulating rollback operation procedures; configuring quick switching entrances; establishing a data rollback mechanism; rollback drills, including: simulating rollback scenarios in test scenarios, and evaluating the impact of rollback operations on each business domain; optimizing rollback processes, and performing training operations.

5. The reconstruction method according to claim 1, characterized in that: Also includes: Performing end-to-end encryption operations on data transmission and storage in the ERP system, including: using national encryption algorithms and international general encryption algorithms to build a multi-level encryption system; performing dynamic desensitization operations on sensitive data in the ERP system to process sensitive data; and performing conditional text anonymization operations for privacy enhancement using private attribute randomization, including: identifying private attributes that need to be anonymized and generating random parameters; applying randomization algorithms to change the private attributes, and reconstructing text content according to conditional text semantics; Perform identity authentication and access control to determine the permission level of the access user and display the data in the ERP system that is compatible with the permission level; A log collection system is set up in the ERP system, including: abnormal behavior detection, including: using a value-penalty-assisted control method without reward or demonstration learning examples and a discrete latent variable enhanced continuous diffusion model to train an anomaly detection model; deploying the anomaly detection model to a working node of the ERP system, detecting abnormal behavior, and generating abnormal behavior alerts and detailed analysis reports.

6. The reconstruction method according to claim 1, characterized in that: Also includes: Conducting a security audit on the source code of the ERP system, including: classifying and grading the source code of the ERP system and generating multi-dimensional security goals; using a multi-objective combinatorial optimization framework synthesized by large-scale hierarchical populations to perform code scanning and perform audit operations on source codes of different types and levels; generating a security audit report and repair suggestions based on the audit operation results; Backing up and restoring the data on the ERP system includes: executing off-site multi-center data backup registration and data backup scheduling based on data priority, wherein the data backup scheduling based on data priority includes: based on dependency-aware priority adjustment technology, analyzing the correlation and dependency between different data in the ERP system to determine the priority of each data on the ERP system; establishing a critical time-sensitive network flow model, preferentially allocating time slots for higher priority data to back up the higher priority data; and adjusting the data priority according to the frequency of data changes and the backup time interval.

7. A distributed ERP system business domain deployment and reconstruction system, characterized in that: include: The processing unit is suitable for sorting out the business functions of each business domain on the ERP system, and the interaction relationship between the data entities of the business functions between different business domains; And, according to the business functions of each business domain, divide it to obtain microservices corresponding to each business domain; The process of combing the business functions of each business domain on the ERP system and the interactive relationships between data entities of business functions between different business domains includes: Based on the collected workflow information of each business domain in the ERP system, a process modeling tool is used to generate a business process diagram, wherein the business process diagram includes the functional relationship and data flow direction of each business function of each business domain; Analyze the database of the ERP system and identify the data entities in each business domain and the interaction relationship between each data entity by establishing an entity relationship diagram; According to the business process diagram, based on the identified business activities, the business functions of each business domain are decomposed into multiple management modules, and according to the calling relationship between each management module, the functional boundary and data entity of each management module and the interaction relationship between each management module are determined; According to the interaction relationship between various management modules and the interaction relationship between various data entities, a data flow diagram between various management modules is constructed, and by identifying the flow path of data entities of various management modules between different management modules, the interaction relationship between data entities of business functions in different business domains is determined; A configuration unit adapted to set the data flow direction between each business domain and between different business domains, and to set the functional interface between each business domain and between different business domains according to the business functions of each business domain and the interaction relationship; A reconstruction unit, adapted to perform database adaptation and source code transformation operations, so that the first database of the ERP system is adapted to the second database of the migration platform system, so as to migrate the microservices corresponding to each business domain, as well as the data entities of each microservice, each business domain, and the data flows between different business domains to the migration platform system, and perform a security check on the migration platform system; A testing unit, adapted to perform independent testing and integration testing on each microservice in the migration platform system, and to perform integration testing and performance testing on the data in the migration platform system, and to generate test results; An execution unit adapted to execute a trial operation based on the test results and to operate it in all business departments in stages; The configuration unit is adapted to set the data flow direction between each business domain and between different business domains according to the business functions of each business domain and the interaction relationship, including: Identify key events in the business functions of each business domain, define the structure and metadata of each key event, and establish a key event processing and routing mechanism to store the data of each business domain in the area corresponding to different routes; select a message queue technology that is compatible with the key events, and use a predefined output transmission protocol format so that the data of each business domain and between different business domains are transmitted in the area corresponding to different routes; The setting of each business domain and the functional interface between different business domains includes: Standardize the functional interfaces of each business domain and between different business domains, and adopt a version control mechanism to plan the abandonment and migration process of functional interfaces; The reconstruction unit is adapted to perform database adaptation and source code transformation operations so that the first database of the ERP system is adapted to the second database of the migration platform system, including: Based on the SQL syntax compatibility test, incompatible SQL statements of the first database and the second database are identified, the incompatible SQL statements are rewritten, and the JOIN operation of the first database is adjusted to adapt to the optimizer of the second database; Using a static code analysis tool, identifying incompatible code segments between the first database and the second database in the running environment, and performing code reconstruction operations to replace incompatible third-party libraries; and modifying and adjusting system calls and network programming interfaces related to process and thread management of the first database; The migrating of the microservices corresponding to each business domain, the data entities of each microservice, each business domain, and the data flows between different business domains to the migration platform system includes: Designing a table structure of the second database and partitioning the table structure so as to distribute and store microservices corresponding to each business domain, data entities of each microservice, each business domain, and data flows between different business domains in different areas; During the migration process, setting the data extraction strategy and data conversion rules of the second database to handle different data types and format differences, and implementing a rollback mechanism; And, setting an index in the table structure to perform a create, modify or delete operation on the data in the second database.

Images