Purchase system and test method thereof, computing device and storage medium
By introducing client tools and testing components into the procurement system, the difference masking between middleware versions and types is achieved, and the adaptation and testing problems during middleware version updates and replacements are solved, saving resources and improving efficiency.
Patent Information
- Application Number
- CN202411396930.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-09
- Publication Date
- 2024-11-01
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The existing procurement system needs to undergo a lot of adaptation and testing when updating the middleware version, resulting in wasting of development and testing resources. When replacing the middleware, it requires full-scene regression testing, which is time-consuming and labor-intensive.
A procurement system was designed, including application components, multiple types of middleware components, client components and test components. The interaction between middleware and application components is realized through client tools, and data playback, data checksum problem alarm is used. The components conduct functional testing, and perform middleware maintenance operations uniformly through operation and maintenance components to block differences between different types and versions.
There is no need to adapt and test the middleware version or type for each application, which saves development and testing resources, reduces update and iteration costs, and improves development efficiency.
Smart Images

Figure CN118885408A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of Internet technology, and in particular to a procurement system and a testing method thereof, a computing device and a storage medium. Background Art
[0002] The procurement system is a supply chain management tool that can help purchasers such as enterprises conduct a series of procurement activities with suppliers, such as procurement, bidding, transactions, contract management, etc. The procurement system can effectively improve procurement efficiency, reduce procurement costs, and strengthen supply chain cooperation.
[0003] Due to the diversity of purchasers, numerous suppliers and the need to cover a variety of categories, the procurement system often contains dozens or even more applications, and each application needs to adapt to various types of middleware. Since different applications have different requirements for the same type of middleware version, and the same application also needs to connect to different versions of middleware when the procurement system version is different, therefore, before deploying the application, it is necessary to adapt and transform the specific version of the middleware and perform other development work and testing. At present, whenever there is a demand for a new version of middleware, it is necessary to carry out adaptation and modification development work and test for that version of middleware separately. The same version of middleware also needs to carry out adaptation and modification development work and test for different versions of procurement systems separately. Moreover, replacement of any middleware requires regression testing of the entire procurement system scenario, which is time-consuming, labor-intensive, inconvenient to use, and greatly wastes development and testing resources. Summary of the invention
[0004] In view of this, the present disclosure provides a procurement system and a testing method thereof, a computing device, and a storage medium.
[0005] According to a first aspect of the present disclosure, there is provided a procurement system, comprising: an application component, multiple types of middleware components, a client component and a test component, each type of middleware component comprising multiple types of middleware, the client component comprising multiple types of client tools, each client tool being used to implement interaction between all middleware in a class of middleware components and the application component, and the test component being used to execute functional test operations of each middleware in a class of middleware components corresponding to the client tool when called by the client tool.
[0006] In some possible implementations of the first aspect of the present disclosure, the test component includes a data replay component, a data verification component and a problem alarm component; wherein the data replay component is used to replay the request received by the client tool and route it to all middleware in a class of middleware components managed by the client tool when called by the client tool; the data verification component is used to verify whether the processing results of the request by each middleware in the class of middleware components managed by the client tool are consistent, and when inconsistency is found, generate a verification result indicating that the processing results are inconsistent; the problem alarm component is used to issue a problem alarm to remind developers based on the verification result generated by the data verification component indicating that the processing results are inconsistent.
[0007] In some possible implementations of the first aspect of the present disclosure, the test component also includes: a data synchronization component, which is used to respond to the operation of the developer and use the verification results generated by the data verification component to level the data in each middleware in a class of middleware components managed by the client tool to eliminate the inconsistency.
[0008] In some possible implementations of the first aspect of the present disclosure, the procurement system further includes: an operation and maintenance component, the operation and maintenance component includes multiple types of operation and maintenance tools, and each type of operation and maintenance tool is used to uniformly perform maintenance operations on each middleware in the same type of middleware components.
[0009] In some possible implementations of the first aspect of the present disclosure, the maintenance operation includes one or more of the following: data table structure change, data correction, theme change, and configuration change.
[0010] In some possible implementations of the first aspect of the present disclosure, the type of the middleware component includes one or more of the following: database, cache middleware, registration center, configuration center, message middleware, object storage service middleware, and search engine middleware.
[0011] According to a second aspect of the present disclosure, a method for testing a procurement system is provided, the method being applied to the procurement system, the method comprising: In response to a request from an external device, the client tool routes the request to the main middleware and calls the data replay component to replay the request to each standby middleware, each of which is a middleware component of the same type as the main middleware but of a different type; The data verification component collects and verifies whether the processing result of the main middleware on the request is consistent with the processing result of each of the standby middlewares on the request, and generates a verification result indicating the inconsistency of the processing results if there is any inconsistency; In response to the verification result indicating that the processing result is inconsistent, the problem alarm component issues a problem alarm to alert the developer.
[0012] In some possible implementations of the second aspect of the present disclosure, the request includes one or more of the following: Business requests; Service instance request for the registry; Service instance requests for the configuration center; File transfer request to the OSS service center.
[0013] In some possible implementations of the second aspect of the present disclosure, the method further includes: in response to the developer's operation, calling the data synchronization component to use the verification result to level the data in the main middleware and / or each backup middleware to eliminate the inconsistency.
[0014] In some possible implementations of the second aspect of the present disclosure, the method further includes: in response to a developer's maintenance operation instruction for a first middleware, calling an operation and maintenance tool corresponding to the first middleware in an operation and maintenance component to perform corresponding maintenance operations on all middleware in the middleware component to which the first middleware belongs.
[0015] According to a third aspect of the present disclosure, a computing device is provided, comprising: one or more processors and a memory storing a program, wherein the program comprises instructions, and when the instructions are executed by the processor, the processor executes the above-mentioned test method of the procurement system.
[0016] According to a fourth aspect of the present disclosure, there is provided a computer-readable storage medium storing a program, wherein the program includes instructions, which, when executed by one or more processors of a computing device, cause the computing device to execute the above-mentioned testing method of the procurement system.
[0017] It can be seen from the above technical solution that in the procurement system of the embodiment of the present invention, no matter which version of the procurement system is, the docking of all applications with the middleware is achieved through client tools, which shields the functional differences and interface differences between different types of middleware and / or different versions of middleware. There is no need to develop a middleware version or middleware type that is compatible with each application separately, nor is there a need to perform separate tests after adaptation. When replacing any middleware, there is no need to perform regression testing on the entire scenario of the procurement system, which greatly saves the development resources and testing resources of the procurement system. At the same time, it also improves the development efficiency of the procurement system and reduces the update and iteration costs of the procurement system. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0019] Figure 1 A schematic diagram of the structure of a procurement system provided in an embodiment of the present disclosure; Figure 2 An example diagram of multiple types of middleware components in a procurement system provided by an embodiment of the present disclosure; Figure 3 A diagram showing an example of a structure of a client component in a procurement system provided in an embodiment of the present disclosure; Figure 4 An example diagram of the interaction between the procurement system and external devices provided in an embodiment of the present disclosure; Figure 5 A flowchart of a procurement system testing method provided by an embodiment of the present disclosure; Figure 6 A schematic diagram of a specific implementation flow of the procurement system testing method provided in an embodiment of the present disclosure. DETAILED DESCRIPTION
[0020] The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.
[0021] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments, and are not intended to limit the present disclosure. The singular forms "a", "said" and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.
[0022] As used herein, the words "if," "if," and the like may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.
[0023] Terminology explanation: Primary middleware: The middleware version most commonly used by users of the procurement system in a certain middleware component. For example, for a database, the primary middleware is usually MySQL.
[0024] Backup middleware: other middleware versions in a middleware component except the main middleware. For example, for a database, all middleware versions except MySQL are backup middleware.
[0025] Figure 1 The structure diagram of the procurement system provided by the embodiment of the present disclosure is shown. Figure 1 As shown, the procurement system includes application components, multiple types of middleware components (for example, n types, n is an integer greater than 1), client components and test components, each type of middleware component includes multiple types of middleware, the client component includes multiple types of client tools (for example, n types, n is an integer greater than 1), each client tool is used to implement the interaction between all middleware in the same type of middleware components and the application components, and the test component is used to perform functional testing operations of each middleware in a type of middleware component corresponding to the client tool when called by a client tool.
[0026] The procurement system may include m types of application components, where m is an integer greater than 1. Each client tool may be used to implement interaction between each application component and all middleware components of the same type.
[0027] From the above, in the procurement system provided by the embodiment of the present disclosure, no matter which version of the procurement system is, the docking of all applications with the middleware is achieved through client tools, which shields the functional differences and interface differences between different types of middleware and / or different versions of middleware. There is no need to develop a middleware version or middleware type that is compatible with each application separately, and there is no need to perform separate tests after adaptation. When replacing any middleware, there is no need to perform regression testing on the entire scenario of the procurement system, which greatly saves development resources and testing resources, while also improving the development efficiency of the procurement system and reducing the update and iteration costs of the procurement system.
[0028] The procurement system provided by the embodiment of the present disclosure may be run on a computing device, which may be, but is not limited to, a computer, a server, or a cluster thereof.
[0029] In the disclosed embodiments, each client tool may integrate the native clients of various middleware components in the same type of middleware components, thereby enabling the interaction between various types of middleware and application components through the client tool.
[0030] Figure 3 A sample diagram showing middleware components in a procurement system. Figure 3In the embodiments of the present disclosure, the types of middleware components may be, but are not limited to, one or more of the following: database, cache middleware, registration center, configuration center, message middleware, object storage service middleware (OSS service middleware), and search engine director level. In specific applications, other middleware may be added or some middleware may be deleted according to application requirements.
[0031] Figure 4 A diagram showing an example of the structure of the client components of a procurement system. Figure 4 The client component may include one or more of the following client tools: message client (MQClient), database client (DBClient), search engine client (ESClient), cache client (CacheClient), registration client (DiscoveryClient), configuration client (ConfigClient), object storage service client (OSSClient).
[0032] MQClient integrates the original clients of the following middleware: RocketMQ4.x, RocketMQ5.x, Kafka, Tong-LINK / Q, etc.
[0033] ESClient integrates the original clients of the following middleware: ES6.x, ES7.x, and ES8.x.
[0034] DBClient integrates the following middleware original clients: MySQL, DAMO, TidB, OceanBase. In addition, DBClient can also integrate the following middleware original clients: Oracle, Renda Jincang.
[0035] Similarly, the cache client (CacheClient), the registration client (DiscoveryClient), the configuration client (ConfigClient), and the object storage service client (OSSClient) also integrate the original clients of each middleware in the corresponding middleware component. This embodiment of the disclosure does not limit this.
[0036] See also Figure 1In the procurement system of the embodiment of the present disclosure, the test component may include: a data replay component, a data verification component and a problem alarm component; wherein the data replay component may be used to replay the request received by the client tool when called by a client tool and route it to all middleware in a class of middleware components managed by the client tool; the data verification component may be used to verify whether the processing results of the requests by each middleware in the class of middleware components managed by the client tool are consistent, and when inconsistency is found, a verification result indicating that the processing results are inconsistent is generated; the problem alarm component may be used to issue a problem alarm to remind developers based on the verification result generated by the data verification component indicating that the processing results are inconsistent.
[0037] The requests received by the client tool may include, but are not limited to: business requests, service instance requests for the registration center, service instance requests for the configuration center, and file transfer requests for the OSS service center. Figure 4 The following is a schematic diagram showing the interaction between the procurement system and external devices according to an embodiment of the present disclosure. Figure 4 , the external device includes a purchaser terminal and a supplier terminal, and the request may come from the purchaser terminal and / or the supplier terminal. Accordingly, the processing result of the request includes one or more of the following: business processing result, service instance registration result, service instance configuration result, and file transfer result.
[0038] The content of the problem alert may be, but not limited to, voice, image, text, video, etc., and the form of the problem alert may be, but not limited to, a problem alert box, a dialog box, or other similar interactive components.
[0039] Figure 4 The following is a schematic diagram showing the interaction between the procurement system and external devices according to an embodiment of the present disclosure. Figure 4 The procurement system can interact with the user device of the developer. Specifically, the problem alarm component can generate a problem alarm containing the verification result in response to the verification result generated by the data verification component indicating that the processing result is inconsistent, and provide the problem alarm to the user device of the developer, and the user device displays it to the developer.
[0040] Further, see Figure 1, the test component may also include: a data synchronization component. The data synchronization component may be used to respond to the developer's operation and use the verification results generated by the data verification component to level the data in each middleware (i.e., the main middleware and / or each backup middleware) in a class of middleware components managed by the client tool to eliminate inconsistencies. Therefore, in the process of handling the inconsistency problem, affected by the inconsistency problem, there may be differences between the relevant data in the main middleware and the relevant data in the backup middleware. After the inconsistency problem is handled through code modification and other methods, the developer can also use the data synchronization component to level the difference to eliminate the impact of the inconsistency problem.
[0041] In some embodiments, see Figure 1 The procurement system may also include: an operation and maintenance component, which includes multiple types of operation and maintenance tools, each type of operation and maintenance tool can be used to uniformly perform maintenance operations on each middleware in the same type of middleware component. As a result, the operation and maintenance operations of each middleware can be uniformly processed using the operation and maintenance tool, which performs verification, replay and orchestration of the maintenance operations, further reducing the operation and maintenance costs of the middleware.
[0042] Different types of middleware components have different types of operation and maintenance operations. In some examples, the operation and maintenance operations may include, but are not limited to, one or more of the following: data table structure changes, data corrections, theme changes, and configuration changes.
[0043] In specific applications, client components and test components can be implemented using languages other than Java or any other language that can communicate with the aforementioned middleware.
[0044] Figure 5 The flowchart of the testing method applicable to the above-mentioned procurement system provided by the embodiment of the present disclosure is shown. Figure 5 , the test method may include the following steps: Step 501, in response to a request from an external device, the client tool routes the request to the main middleware and simultaneously calls the data replay component to replay and request to each backup middleware, each backup middleware and the main middleware are middleware components of the same type but of different types; Step 502, the data verification component collects and verifies whether the processing result of the main middleware on the request is consistent with the processing result of each backup middleware on the request, and generates a verification result indicating that the processing result is inconsistent if there is any inconsistency; Step 503: In response to the verification result indicating that the processing result is inconsistent, the problem alarm component issues a problem alarm to alert the developer.
[0045] In the testing method of the embodiment of the present disclosure, specific details such as "request" can be found in the description of the procurement system section above and will not be repeated here.
[0046] Taking the login interface as an example, when a user clicks the login interface to log in to the procurement system, the steps related to the middleware component in the processing flow of the login interface include the following steps a1 to a4: Step a1, query, that is, query the database according to the username and password to verify the validity of the username and password; Step a2: After successful login, use cache data to record the user login status; Step a3, sending an MQ message to notify the log system; Step a4. After receiving the MQ message, the log system writes the login log to the ES middleware.
[0047] During the normal processing of the login interface, the testing method of the embodiment of the present disclosure can be used to simultaneously perform functional tests of the middleware involved in steps a1 to a4.
[0048] Step a1 involves database middleware. The test method of the embodiment of the present disclosure is used to perform a test on the functions related to the database middleware. The test process may include: a client tool corresponding to the database middleware ( Figure 3 The database client (DBClient) shown in the figure responds to the query request. When querying the database according to the username and password, the data replay component is called to send the query request to the four versions of the database in the database middleware at the same time, namely MySQL, DAMO, TiDB, and OceanBase. After the four databases return the processing results, the data verification component is called to verify the processing results returned by the four databases. If the processing results returned by the four databases are consistent, a first verification result indicating that the processing results are consistent is generated. If one or some of the four databases have situations such as data syntax not supported and / or database data inconsistency, it indicates that the processing results returned by the four databases are inconsistent, and a second verification result indicating that the processing results are inconsistent is generated. In response to the second verification result, the problem alarm component collects problems according to the second verification result, and sends the problem in the form of a problem alarm according to the type of problem and the application where the problem occurs, such as an instant messaging tool, to remind developers to make improvements.
[0049] Step a2 involves cache middleware, and the test method of the embodiment of the present disclosure can also be used to perform testing of cache middleware related functions. The test process is the same as the test process of the aforementioned step a1. The difference is that the request type is a cache request, involving 4 versions of cache middleware, namely Redis, TongRDS, Memcached, and MongoDB.
[0050] Step a3 involves message middleware, and the test method of the embodiment of the present disclosure can also be used to perform testing of message middleware related functions. The test process is the same as the test process of the aforementioned step a1. The difference is that the request type is a message queue request, involving 4 versions of message middleware, namely RocketMQ4, RocketMQ5, Kafka, and Tong-LINK / Q.
[0051] Step a4 involves ES middleware, and the test method of the embodiment of the present disclosure can also be used to perform tests on ES middleware related functions. The test process is the same as the test process of the aforementioned step a1. The difference is that the request type is a file upload request or a file download request, involving three versions of ES middleware, namely ES6, ES7, and ES8.
[0052] Figure 6 A specific implementation flow chart of the testing method for the procurement system provided by an embodiment of the present disclosure is shown.
[0053] Further, see Figure 6 The above-mentioned testing method may further include: step 504, in response to the operation of the developer, calling the data synchronization component to use the verification result to level the data in the main middleware and / or each backup middleware (i.e., each middleware in a class of middleware components managed by the client tool) to eliminate inconsistencies.
[0054] Taking step a4 of the aforementioned login interface as an example, when the log system writes the login log to the ES middleware after receiving the message, if the ES6 middleware and ES7 middleware are written successfully, but the ES8 middleware fails to write, the data verification component will generate a verification result indicating that the ES8 middleware failed to write. After receiving the problem alert and solving the problem, the developer can use the data synchronization component to flatten the data in the ES8 middleware with the data in the ES6 middleware or ES7 middleware to eliminate the differences between the ES8 middleware and other ES middleware, and eliminate the inconsistency problem. If the flattening process is not performed, all subsequent requests to query the login log will be reported as errors. This situation is effectively avoided by the flattening operation of the above-mentioned data synchronization component.
[0055] Further, see Figure 6 The above test method may further include: step 505, in response to the developer's maintenance operation instruction for the first middleware, calling the operation and maintenance tool corresponding to the first middleware in the operation and maintenance component to perform corresponding maintenance operations on all middleware in the middleware component to which the first middleware belongs. The first middleware is any middleware in any middleware component in the procurement system.
[0056] For example, if the user table in the database middleware needs to add a new account validity period field, developers do not need to perform the modification of adding this field for the four databases of MySQL, DAMO, TiDB, and OceanBase respectively. They only need to add the account validity period field to the operation and maintenance tool of the database middleware, and the operation and maintenance tool will add this field to the four databases respectively. For example, the message middleware needs to add a new topic, the ES middleware needs to add a new index, and the configuration center needs to modify a configuration. It can be seen that the operation and maintenance components can effectively improve the maintenance efficiency of different middleware, reduce maintenance costs, and save development resources during maintenance.
[0057] It should be noted that step 505 may be executed simultaneously with any of the aforementioned steps 501 to 504 , may be executed after step 504 , or may be executed before step 501 .
[0058] Similar to the aforementioned login interface, if there are other processing flows involving middleware, the testing method of the disclosed embodiment can be applied to perform testing of middleware-related functions.
[0059] For example, when an application obtains a service instance from a registration center, the registration center is involved. At this time, the registration client (DiscoverClient) can be used to test various versions of middleware (for example, Eureka, Nacos, Etcd, etc.) in the registration center using the testing method of the embodiment of the present disclosure.
[0060] For another example, when an application obtains a service instance from a configuration center, the configuration center is involved. At this time, the configuration client (ConfigClient) can be used to test various versions of middleware (for example, Apollo, Nacos, Etc, etc.) in the configuration center using the testing method of the embodiment of the present disclosure.
[0061] For another example, when uploading and downloading files based on object storage involves OSS service middleware, OSSClient can be used to test various versions of middleware in the OSS service middleware (for example, Alibaba Cloud OSS, Tencent Cloud COS, Huawei Cloud OBS, Amazon S3, Minio, etc.) using the testing method of the embodiment of the present disclosure.
[0062] The present disclosure also provides a computing device, which includes one or more processors and a memory storing a program, wherein the program includes instructions, and when the instructions are executed by the processor, the processor executes the aforementioned test method of the procurement system. The computing device can be implemented as an electronic device, a computer, a server, or a cluster thereof.
[0063] In addition, an embodiment of the present disclosure further provides a computer-readable storage medium on which a computer program is stored. The program includes instructions, and when the instructions are executed by one or more processors of a computing device, the steps of the aforementioned procurement system testing method are executed.
[0064] The above-mentioned programs (also referred to as software, software applications, or codes) include machine instructions for programmable processors, and these computer programs may be implemented using object-oriented programming languages, assembly or machine languages.
[0065] With the development of time and technology, the meaning of medium is becoming more and more extensive, and the dissemination path of computer programs is no longer limited to tangible media, but can also be downloaded directly from the Internet. Any combination of one or more computer-readable storage media can be used. Computer-readable storage media can be used, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples of computer-readable storage media (a non-exhaustive list) include: portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this document, computer-readable storage media can be any tangible medium that contains or stores a program that can be used by or in combination with an instruction execution system, device or device.
[0066] The technical solution provided by the present disclosure is described in detail above. The principles and implementation methods of the present disclosure are described in detail using specific examples. The description of the above embodiments is only used to help understand the method and core idea of the present disclosure. At the same time, for those skilled in the art, according to the idea of the present disclosure, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting the present disclosure.
[0067] The above description is only a preferred embodiment of the present disclosure and is not intended to limit the present disclosure. Any modifications, equivalent substitutions, etc. made within the spirit and principles of the present disclosure should be included in the protection scope of the present disclosure.
Claims
1. A purchasing system, characterized in that: It includes: application components, multiple types of middleware components, client components and test components, each type of middleware component includes multiple types of middleware, the client components include multiple types of client tools, each client tool is used to realize the interaction between all middleware in a type of middleware components and application components, and the test component is used to execute functional test operations of each middleware in a type of middleware components corresponding to the client tool when called by one of the client tools.
2. The purchasing system according to claim 1, characterized in that: The test components include a data replay component, a data verification component and a problem alarm component; wherein, The data replay component is used to replay and route the request received by the client tool to all middlewares in a class of middleware components managed by the client tool when called by the client tool; The data verification component is used to verify whether the processing results of the request by each middleware in the class of middleware components managed by the client tool are consistent, and generate a verification result indicating that the processing results are inconsistent when inconsistency is found; The problem alarm component is used to issue a problem alarm to remind developers according to the verification result generated by the data verification component and indicating that the processing result is inconsistent.
3. The purchasing system according to claim 2, characterized in that: The test component also includes: a data synchronization component, which is used to respond to the operation of the developer and use the verification result generated by the data verification component to level the data in each middleware in a class of middleware components managed by the client tool to eliminate the inconsistency.
4. The purchasing system according to claim 1, characterized in that: The procurement system further includes: an operation and maintenance component, which includes multiple types of operation and maintenance tools, each type of operation and maintenance tool is used to uniformly perform maintenance operations on each middleware in the same type of middleware components.
5. The purchasing system according to claim 4, characterized in that: The maintenance operation includes one or more of the following: data table structure change, data correction, theme change, configuration change.
6. The purchasing system according to claim 1, characterized in that: The types of the middleware components include one or more of the following: database, cache middleware, registration center, configuration center, message middleware, object storage service middleware, and search engine middleware.
7. A testing method for a procurement system, characterized in that: The method is applied to the procurement system according to any one of claims 1 to 6, and the method comprises: In response to a request from an external device, the client tool routes the request to the main middleware and simultaneously calls the data replay component to replay the request to each standby middleware, each of which is a middleware component of the same type as the main middleware but of a different type; The data verification component collects and verifies whether the processing result of the main middleware on the request is consistent with the processing result of each of the backup middlewares on the request, and generates a verification result indicating that the processing results are inconsistent if there is any inconsistency; In response to the verification result indicating that the processing result is inconsistent, the problem alarm component issues a problem alarm to alert the developer.
8. The method according to claim 7, characterized in that The request includes one or more of the following: Business requests; Service instance request for the registry; Service instance requests for the configuration center; File transfer request to the OSS service center.
9. The method according to claim 7, characterized in that: The method further comprises: In response to the operation of the developer, the data synchronization component is called to use the verification result to level the data in the main middleware and / or each standby middleware to eliminate the inconsistency.
10. The method according to claim 7, characterized in that The method further comprises: In response to a maintenance operation instruction from a developer for a first middleware, an operation and maintenance tool corresponding to the first middleware in an operation and maintenance component is called to perform a corresponding maintenance operation on all middleware in a middleware component to which the first middleware belongs.
11. A computing device, characterized in that: include: One or more processors and a memory storing a program, wherein the program includes instructions, and when the instructions are executed by the processor, the processor executes the method according to any one of claims 7 to 10.
12. A computer-readable storage medium storing a program, wherein the program includes instructions, which, when executed by one or more processors of a computing device, cause the computing device to perform the method according to any one of claims 7 to 10.
Citation Information
Patent Citations
Method for querying data through database middleware and database middleware
CN104063425A
Mixed data source plug-in calling system and calling method
CN112363781A
Cross-platform universal database access middleware
CN114860756A
Agent method and device for mixed use of multiple databases
CN116126865A
Health state checking method, device and equipment and storage medium
CN116841902A
