A Mimicry Executor Database Design Method and System

Abstract

This invention proposes a database design method and system for mimicking executors, comprising: designing a database for a mimicking system including a database client and a baseline database, and placing an adjudicator at the back end of the database; the database client interacts with each online executor to obtain the database of each online executor, obtain the data tables under the database, obtain the content of the data tables, and finally send the obtained data to the adjudicator; the adjudicator adjudicates the database, data tables, and database tables, and updates the baseline database with the data of the successful adjudication; when the adjudicator detects abnormal database content, it notifies the scheduler to clean the executor or schedule a new executor to come online; based on the baseline database, the scheduler restores the database content of the executor to be cleaned; the scheduler retrieves data from the baseline database to synchronize the data of the newly online executor.

Description

Technical Field

[0001] This invention belongs to the field of mimicry defense technology, and in particular relates to a mimicry execution entity database design method and system. Background Technology

[0002] Traditional applications typically store business data using databases. When performing mimicry transformation on traditional applications, the design of the execution unit database is inevitably involved. Currently, mimicry application transformation solutions often involve multiple execution units sharing a single database, while placing the adjudicator in front of the database, such as... Figure 1 As shown, when an executor interacts with the database, it must first pass through an adjudicator. The adjudicator contains a database protocol parsing module. Data requests sent by each executor are sent to this module, which then adjudicates the data requests before forwarding the adjudicated data to the database. This method solves the database synchronization problem. However, the adjudicator is located at the database front end. Since commonly used databases include MySQL, Oracle, SQL Server, and domestically developed databases, which often employ different database protocols, the protocol parsing module needs to adapt to these protocols. This increases the design complexity and versatility of the adjudicator, resulting in weak versatility for the mimicry executor-shared database.

[0003] Therefore, providing a general database design method in a simulated environment is of great significance for reducing the development difficulty of simulated applications. Summary of the Invention

[0004] To address the aforementioned issues, it is necessary to provide a method and system for designing a mimicry execution entity database.

[0005] The first aspect of this invention provides a database for a mimicry system, comprising: a database client and a baseline database;

[0006] The database client is used to obtain the databases of each online executor in the mimicry system, obtain data tables based on the obtained databases, and then obtain the contents of the data tables based on the data tables; it is used to send the obtained databases, data tables, and database table contents to the adjudicator; it is also used to send the updated data to the scheduler when performing executor cleaning or data synchronization of newly online executors.

[0007] The baseline database is used to receive and update data that has been successfully adjudicated by the adjudicator; it is also used as the basis for restoring the database content of the execution body when the adjudicator detects abnormal database content and performs execution body cleaning, and as the basis for synchronizing the data of newly launched execution bodies.

[0008] Based on the above, the benchmark database uses MySQL, Oracle, SQL Server, or a domestic database.

[0009] Based on the above, the databases of each online execution entity are independent databases, using any one of MySQL, Oracle, SQL Server, or domestic databases.

[0010] Based on the above, the database client interacts with each online executor through standard SQL statements to obtain data from the databases of each online executor in the mimicry system.

[0011] A second aspect of the present invention provides a method for designing a mimicry system database, comprising the following steps: designing the database for the mimicry system and placing an adjudicator at the back end of the database;

[0012] The database client first interacts with each online executor to obtain the database of each online executor, then obtains the data tables under the database, then obtains the content of the data tables, and finally sends the obtained database, data tables, and database table content to the adjudicator.

[0013] The adjudicator adjudicates the database, data table, and database table, and updates the benchmark database with the data that is successfully adjudicated.

[0014] When the arbiter detects an anomaly in the database content, it notifies the scheduler to clean the executor or schedule a new executor to come online.

[0015] When performing execution unit cleaning, the scheduler restores the contents of the execution unit database to be cleaned based on the baseline database.

[0016] When a new executor is scheduled to come online, the scheduler retrieves data from the baseline database to synchronize the data of the newly launched executor.

[0017] A third aspect of the present invention provides a mimicry executor database system, including an online executor, an adjudicator, and a scheduler, wherein the mimicry executor database design method is adopted when designing the mimicry executor database.

[0018] Based on the above, the database used for the mimicry system is implemented using a separate database server.

[0019] The beneficial effects of this invention are as follows:

[0020] The invention solves the problem of low compatibility when using a shared database for the mimicry executor by adopting an independent database and placing the adjudicator at the database backend, thus accelerating the efficiency of mimicry transformation of traditional applications.

[0021] Additional aspects and advantages of the invention will become apparent in the following description or may be learned by practice of the invention. Attached Figure Description

[0022] Figure 1 This is a schematic diagram of the database structure of Embodiment 1 of the present invention. Detailed Implementation

[0023] To better understand the above-mentioned objectives, features, and advantages of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be combined with each other.

[0024] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and therefore the scope of protection of the invention is not limited to the specific embodiments disclosed below.

[0025] Example 1

[0026] like Figure 1 As shown, this embodiment provides a database for a mimicry system, including: a database client and a benchmark database;

[0027] The database client interacts with each online executor through standard SQL statements to obtain (at a frequency of approximately 1 second) the databases of each online executor in the mimicry system, retrieve data tables from the obtained databases, and then retrieve the contents of the data tables. It is used to send the obtained databases, data tables, and database table contents to the adjudicator. It is also used to send the updated data to the scheduler when performing executor cleaning or synchronizing data of newly launched executors.

[0028] The baseline database is used to receive and update data that has been successfully adjudicated by the adjudicator; it is also used as the basis for restoring the database content of the execution body when the adjudicator detects abnormal database content and performs execution body cleaning, and as the basis for synchronizing the data of newly launched execution bodies.

[0029] The data update method in this embodiment can be incremental update, which updates the newly added data by appending, deleting or inserting; or full update, which updates the entire data content.

[0030] Specifically, the benchmark database uses MySQL, Oracle, SQL Server, or a domestically developed database. Each online executable uses an independent database, employing any one of MySQL, Oracle, SQL Server, or a domestically developed database.

[0031] Example 2

[0032] This embodiment provides a method for designing a mimicry execution entity database, including the following steps: designing the database for the mimicry system as described in Embodiment 1, and placing the adjudicator at the back end of the database;

[0033] The database client first interacts with each online executor (taking three online executors as an example) to obtain the databases DB1, DB2, and DB3 of each online executor. Then, it obtains the data tables {DB1-T1, DB1-T2, DB1-T3}, {DB2-T1, DB2-T2, DB2-T3}, and {DB1-T1, DB1-T2, DB1-T3} under the database. Next, it obtains the contents of the data tables. Finally, it sends the obtained databases, data tables, and database table contents to the adjudicator.

[0034] The adjudicator adjudicates databases, data tables, and database tables, and updates the base database with the data that has been adjudicated successfully. Specifically, the adjudication of databases, data tables, and database tables is carried out by either a complete comparison of key data characters or by compressing the data and then comparing it. If they match, the adjudication is successful.

[0035] When the arbiter detects an anomaly in the database content, it notifies the scheduler to clean the executor or schedule a new executor to come online.

[0036] When performing execution unit cleaning, the scheduler restores the contents of the execution unit database to be cleaned based on the baseline database.

[0037] When a new executor is scheduled to come online, the scheduler retrieves data from the baseline database to synchronize the data of the newly launched executor.

[0038] Example 3

[0039] The third aspect of the present invention provides a mimicry executor database system, including an online executor, an adjudicator, and a scheduler. When designing the mimicry executor database, the mimicry executor database design method described in Example 1 is adopted.

[0040] Specifically, the database used for the mimicry system is implemented using a separate database server.

[0041] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for designing a database of mimetic executors, characterized by The method comprises the following steps: designing a database for the quasimodo system and placing a resolver at the back end of the database; the database for the quasimodo system comprises a database client and a benchmark database; the database client is used to interact with each online executor through a standard sql statement, acquire the database of each online executor in the quasimodo system, acquire a data table according to the acquired database, acquire the content in the data table according to the data table, send the acquired database, data table and database table content to the resolver, and send the updated data to the dispatcher when performing executor cleaning or data synchronization of a newly online executor; the benchmark database is used to receive and update the data successfully resolved by the resolver, and is used as a basis for restoring the database content of the executor when the resolver detects that the database content is abnormal and performs executor cleaning, and is used as a basis for data synchronization of the newly online executor when the newly online executor is online; the database client first interacts with each online executor, acquires the database of each online executor, then acquires a data table under the database, then acquires the content in the data table, and finally sends the acquired database, data table and database table content to the resolver; the resolver resolves the database, data table and database table, and updates the successfully resolved data to the benchmark database; when the resolver detects that the database content is abnormal, the dispatcher is notified to clean the executor or schedule a new executor to be online; when the executor is cleaned, the dispatcher restores the database content of the executor to be cleaned according to the benchmark database; when the new executor is scheduled to be online, the dispatcher synchronizes the data of the new online executor according to the data from the benchmark database.

2. The method of claim 1, wherein, The benchmark database adopts mysql, oracle, SqlServer or a domestic database.

3. The method of claim 1, wherein, The database of each online executor is an independent database, which adopts any one of mysql, oracle, SqlServer and a domestic database.

4. A database system of a stigmergic executor, comprising an online executor, an arbiter and a dispatcher, characterized in that: When the database of the quasimodo executor is designed, the quasimodo executor database design method in any one of claims 1-3 is adopted.

5. The system of claim 4, wherein: The database for the quasimodo system is implemented by using an independent database server.

Images