CN111475400A - A verification method for a business platform and related equipment - Google Patents

Abstract

The embodiment of the present application discloses a verification method for a business platform and related equipment. The method is applied to the technical field of testing, including: when a server receives a data access request sent by the business platform after going online, it can select a rule based on a preset A target database matching the domain name carried in the data access request is determined from at least two preset databases, and a data operation corresponding to the data access request is performed through the target database. By implementing the embodiments of the present application, for data access based on different domain names, different target databases can be used to perform data operations, thereby effectively realizing the verification of the online business platform.

Description

A verification method for a business platform and related equipment

technical field

The invention relates to the technical field of testing, in particular to a verification method and related equipment of a business platform.

Background technique

When the development of the business platform is completed or the version is changed, it is usually necessary to verify the business platform before going online. However, it is difficult for the test, development environment deployment, network situation, historical data, configuration and other information to be completely consistent with the configuration of the production environment. After the business platform goes online, development, testing, operation and other personnel cannot verify the business platform in the production environment (that is, after going online). It is unknown whether the content of this online change is normal and whether the functional process can be used normally. Only when the user uses it can it be exposed, and the problem cannot be found and solved in time. Therefore, how to realize the verification of the business platform in the production environment has become an urgent problem to be solved.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a service platform verification method and related equipment, which can efficiently realize the verification of the online service platform.

The first aspect The embodiment of the present application provides a verification method for a business platform, the method is applied to a server corresponding to the business platform, and the method includes:

Receive a data access request carrying a domain name sent by the business platform after going online, where the domain name includes a verification domain name or a production domain name, and the verification domain name is used for the first user to verify the business platform in a production environment, so the domain name includes a verification domain name or a production domain name. The production domain name is used for the second user to access the business platform in the production environment;

Determine a target database matching the domain name from at least two preset databases based on a preset selection rule;

The data operation corresponding to the data access request is performed by using the target database, and the data operation includes data query and/or data writing.

In one embodiment, the at least two preset databases include a production database and a verification database, and the specific implementation of determining a target database matching the domain name from the at least two preset databases based on a preset database selection rule The way is:

If it is detected that the domain name carried in the data access request is a verification domain name, the verification token carried in the data access request is compared with the preset verification token under the verification domain name;

If the comparison shows that the verification token matches the preset verification token, the verification database is determined from at least two preset databases as the target database matching the verification domain name.

In one embodiment, after the verification token carried in the data access request is compared with the preset verification token under the verification domain name, the verification token and the preset verification token may be obtained by comparison. If the cards do not match, the production database is determined from at least two preset databases as the target database matching the verification domain name.

In one embodiment, the at least two preset databases include a production database and a verification database, and the specific implementation of determining a target database matching the domain name from the at least two preset databases based on a preset database selection rule The method is as follows: if it is detected that the domain name carried in the data access request is the production domain name, the production database is determined from at least two preset databases as the target database matching the production domain name.

In one embodiment, at least one test case can also be used to verify the online business platform in a production environment; if it is detected that the first test case fails to verify the online business platform, determine The business platform of the current version runs incorrectly, and the first test case is any one of the at least one test case; and a version rollback operation is performed on the business platform of the current version.

In one embodiment, before the version rollback operation is performed on the current version of the business platform, an exception type corresponding to the failed verification may also be detected; if the exception type is a preset type, the execution of the The steps of performing a version rollback operation on the current version of the service platform are described, and the preset type includes a null pointer exception or a service exception.

In one embodiment, if it is detected that the first test case fails the verification of the online business platform, it is also possible to determine whether the abnormality type corresponding to the failed verification is a sub-module abnormality of the business platform or Log abnormality; if it is determined that the abnormality type corresponding to the failed verification is the submodule abnormality or the log abnormality, output alarm information.

In a second aspect, an embodiment of the present application provides an apparatus for verifying a service platform, where the apparatus for verifying a service platform includes a module for executing the method of the first aspect above.

In a third aspect, an embodiment of the present application provides a server, the server includes a processor, a network interface, and a memory, the processor, the network interface, and the memory are connected to each other, wherein the network interface is controlled by the processor For sending and receiving messages, the memory is used to store a computer program for supporting the server to execute the above method, the computer program includes program instructions, and the processor is configured to invoke the program instructions to execute the method of the first aspect.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program includes program instructions that, when executed by a processor, cause all The processor executes the method of the first aspect.

In this embodiment of the present application, when the server receives a data access request sent by the business platform after going online, it may determine a target database matching the domain name carried in the data access request from at least two preset databases based on preset selection rules , and perform data operations corresponding to data access requests through the target database. For data access based on different domain names, different target databases can be used to perform data operations, so as to efficiently verify the online business platform.

Description of drawings

In order to explain the technical solutions of the embodiments of the present application more clearly, the following will briefly introduce the accompanying drawings used in the description of the embodiments. For those of ordinary skill, other drawings can also be obtained from these drawings without any creative effort.

1 is a schematic structural diagram of a verification system of a business platform provided by an embodiment of the present application;

2 is a schematic flowchart of a verification method for a business platform provided by an embodiment of the present application;

3 is a schematic flowchart of a verification method for another business platform provided by an embodiment of the present application;

4 is a schematic block diagram of a verification device for a service platform provided by an embodiment of the present application;

FIG. 5 is a schematic block diagram of a server provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

Referring to FIG. 1 , it is a verification system for a business platform provided by an embodiment of the present application. The verification system includes a business platform 100 and a server 200 corresponding to the business platform. The server is preset with at least two databases, including a production database and a verification database. In one embodiment, a production domain name and a verification domain name may be pre-configured, the verification domain name is used for the first user to verify the business platform in the production environment, and the production domain name is used for the second user to access the business platform in the production environment. Among them, the first user can be understood as a person who needs to verify the business platform for development, testing, operation, etc. The first user accesses the business platform after going online and uses the verification domain name, and uses the verification domain name to verify the business platform in the production environment. Verify; the second user is an ordinary user using the business platform, and the second user accesses the online business platform using the production domain name.

Further, the first user or the second user can send a data access request carrying its own corresponding domain name to the server 200 through the business platform 100, and when the server 200 receives the data access request carrying the domain name sent by the business platform 100 after going online, A target database matching the domain name can be determined from at least two preset databases based on preset selection rules, and a data operation corresponding to the data access request is performed through the target database, and the data operation includes data query and/or data writing . Wherein, the target database includes a production database or a verification database. By implementing the embodiments of the present application, when receiving data access requests from different domain names, a target database matching the domain names can be used to perform data operations corresponding to the data access requests, and on the one hand, data generated by data access under different domain names can be isolated from each other. , will not contaminate each other; on the other hand, the first user can verify the business platform in the production environment by verifying the domain name, and effectively realize the verification of the business platform in the production environment.

It can be understood that the verification system of the business platform described in the embodiments of the present application is for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and does not constitute a limitation on the technical solutions provided by the embodiments of the present application. It can be seen that, with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

Referring to FIG. 2, FIG. 2 is a schematic flowchart of a verification method of a business platform provided by an embodiment of the present application. The method is applied to a server and can be executed by the server. As shown in the figure, the verification method of the business platform may include:

S201: Receive a data access request carrying a domain name sent by the business platform after going online, where the domain name includes a verification domain name or a production domain name, the verification domain name is used for the first user to verify the business platform in the production environment, and the production domain name is used for The second user accesses the business platform in the production environment.

In one embodiment, the developer can pre-configure a production domain name and a verification domain name, where the verification domain name is used for the first user to verify the service platform in the production environment, and the production domain name is used for the second user to access the service in the production environment platform. Among them, the first user can be understood as a person who needs to verify the business platform for development, testing, operation, etc. The first user accesses the business platform after going online and uses the verification domain name, and uses the verification domain name to verify the business platform in the production environment. Verify; the second user is an ordinary user using the business platform, and the second user accesses the online business platform using the production domain name.

In one embodiment, the first user can access the business platform by verifying the domain name. In this case, the business platform can generate a data access request carrying the verification domain name, and send the data carrying the verification domain name to the server corresponding to the business platform. access request.

In one embodiment, the second user can access the business platform through the production domain name. In this case, the business platform can generate a data access request carrying the production domain name, and send the data carrying the production domain name to the server corresponding to the business platform. access request.

S202: Determine a target database matching the domain name from at least two preset databases based on a preset selection rule.

S203: Execute a data operation corresponding to the data access request through the target database, where the data operation includes data query and/or data writing.

Wherein, the above-mentioned at least two preset databases include a production database and a verification database. In one embodiment, the server may determine a target database matching the domain name from at least two preset databases based on a preset selection rule, where the target database includes a production database or a verification database, and further, execute a data access request through the target database corresponding data operations. Using the target database matching the domain name to perform the data operation corresponding to the data access request can make the data generated in the business platform based on the data access of different domain names stored in different target databases, so that the data are isolated from each other and will not pollute each other. Not only is it beneficial to ensure efficient verification of the business platform in the production environment, but also the data generated during the verification process does not affect the access of the second user, thereby ensuring the performance of the business platform.

In this embodiment of the present application, when the server receives a data access request sent by the business platform after going online, it may determine a target database matching the domain name carried in the data access request from at least two preset databases based on preset selection rules , and perform data operations corresponding to data access requests through the target database. For data access based on different domain names, different target databases can be used to perform data operations, so as to efficiently verify the online business platform.

Referring to FIG. 3, FIG. 3 is a schematic diagram of another verification method of a business platform provided by an embodiment of the present application. The method is applied to a server and can be executed by the server. As shown in the figure, the verification method of the business platform may include:

S301: Receive a data access request carrying a domain name sent by the business platform after going online, the domain name includes a verification domain name or a production domain name, the verification domain name is used for the first user to verify the business platform in the production environment, and the production domain name is used for The second user accesses the business platform in the production environment.

S302: If it is detected that the domain name carried in the data access request is a verification domain name, compare the verification token carried in the data access request with a preset verification token under the verification domain name.

S303: If the verification token matches the preset verification token by comparison, determine the verification database from at least two preset databases as the target database matching the domain name. Wherein, the at least two preset databases include a production database and a verification database.

In one embodiment, after the server compares the verification token carried in the data access request with the preset verification token under the verification domain name, if the verification token does not match the preset verification token from the comparison, at least two In the preset database, the production database is determined as the target database matching the domain name.

In one embodiment, all requests for access through the verification domain name will carry a verification-token (verification token) request header, and the developer can pre-configure the verification token under the verification domain name (that is, the preset verification token) . In this case, when the server receives the data access request carrying the domain name sent by the business platform after going online, it can detect whether there is a verification token from the request header of the data access request, and if so, carry the data access request with The verification token is compared with the preset verification token, and if the verification token carried in the data access request is the same as the preset verification token, it can be determined that the verification token matches the preset verification token. If the verification token carried in the data access request is different from the preset verification token by comparison, it can be determined that the verification token does not match the preset verification token.

In another embodiment, if the server detects that the domain name carried in the data access request is the production domain name, the server may determine the production database from at least two preset databases as the target database matching the production domain name.

S304: Execute a data operation corresponding to the data access request through the target database, where the data operation includes data query and/or data writing.

In one embodiment, after the target database is determined, all data query and writing in this data access process are completed through the target database, thereby realizing the verification of the business platform in the production environment.

In one embodiment, the data access request in step S301 is sent when the online business platform is verified in a production environment based on at least one test case. In this case, the server can use at least one test case to verify the online business platform in the production environment, and if it is detected that the first test case fails to verify the online business platform, then determine the current version of the business platform. The business platform runs incorrectly, and the first test case is any one of at least one test case. Further, the server performs a version rollback operation on the current version of the business platform.

In one embodiment, the specific implementation of the server performing a version rollback operation on the current version of the business platform is: obtaining the deployment file of the business platform of the previous historical version corresponding to the current version, and the current version of the business platform. The platform is canceled online, and based on the deployment file, the business platform of the previous historical version is redeployed, thereby implementing the version rollback operation of the current version of the business platform.

For example, the verification domain name of the business platform is https://www.validation-dev.pazhengfuyun.com. In this case, after the new version is launched, testers and developers can pass https://www. The domain name validation-dev.pazhengfuyun.com accesses the business platform. Use test cases to verify whether the functional parts changed after the version goes online can be used normally. If there are test cases that fail, it means that the current version still has problems that affect the normal operation of the application. , at this time, roll back the version, redeploy the application that ran well last time, and cancel the current launch.

Exemplarily, assuming that the current version of the business platform is the business platform of version 2.1, if the version rollback operation of the current version of the business platform is required, the business platform of version 2.1 can be cancelled and the business platform of version 2.0 can be redeployed.

In one implementation, before the server performs the version rollback operation on the current version of the business platform, it can also detect the corresponding exception type that fails the verification, and if the exception type is a preset type, trigger the execution of the current version of the business platform Steps for performing a version rollback operation. The preset type includes null pointer exceptions or business exceptions.

In another embodiment, if the server detects that the verification of the online business platform by the first test case fails, it determines whether the abnormal type corresponding to the failed verification is a sub-module abnormality or log abnormality of the business platform. If the corresponding exception type that fails the verification is a submodule exception or a log exception, an alarm message is output. The alarm information is used to indicate that the submodule is abnormal or the log is abnormal.

In one embodiment, if the server determines that the exception type corresponding to the failed verification is a sub-module exception, the server may perform a version rollback operation for the sub-module. The sub-module may be a functional module corresponding to the business platform, or a subsystem (eg, a user login system).

In one embodiment, in the above-mentioned test process, in order to avoid the impact of server overload on the business platform in the production environment, the maximum load capacity of the production environment can be verified through a stress test. Specifically, the server can call the stress testing tool to verify the maximum concurrency and throughput of the production environment, which facilitates adjustment of the hardware configuration of the production environment to ensure that the system can operate normally under high concurrency and high throughput conditions. In the embodiment of the present application, when the server detects that the domain name carried in the data access request is a verification domain name, it can compare the verification token carried in the data access request with the preset verification token under the verification domain name, and if the verification token is obtained from the comparison If the token matches the preset verification token, the verification database is determined from at least two preset databases as the target database matching the domain name, and the data operation corresponding to the data access request is performed through the verification database. The verification of the business platform in the production environment can be efficiently tested.

The embodiment of the present application also provides a verification device for a service platform. The apparatus includes a module for executing the method described in FIG. 2 or FIG. 3 , and is configured on the server. Specifically, referring to FIG. 4 , it is a schematic block diagram of a verification apparatus of a service platform provided by an embodiment of the present application. The verification device of the service platform of this embodiment includes:

The communication module 40 is configured to receive a data access request carrying a domain name sent by the business platform after going online, where the domain name includes a verification domain name or a production domain name, and the verification domain name is used for The business platform performs verification, and the production domain name is used for the second user to access the business platform in the production environment;

a processing module 41, configured to determine a target database matching the domain name from at least two preset databases based on a preset selection rule;

The processing module 41 is further configured to perform a data operation corresponding to the data access request through the target database, where the data operation includes data query and/or data writing.

In one embodiment, the at least two preset databases include a production database and a verification database, and the processing module 41 is specifically configured to, if it is detected that the domain name carried in the data access request is a verification domain name, carry the data access request with The verification token is compared with the preset verification token under the verification domain name; if it is found that the verification token matches the preset verification token, the verification database is determined from at least two preset databases as The verification domain name matches the target database.

In one embodiment, the processing module 41 is further configured to determine, from at least two preset databases, that the production database is the same as the verification token if the verification token does not match the preset verification token. The target database for domain name matching.

In one embodiment, the at least two preset databases include a production database and a verification database, and the processing module 41 is specifically configured to, if it is detected that the domain name carried in the data access request is a production domain name, select from the at least two preset databases The production database is determined as the target database matching the production domain name.

In one embodiment, the processing module 41 is further configured to verify the online business platform through at least one test case in a production environment; if it is detected that the first test case does not verify the online business platform If the test is passed, it is determined that the business platform of the current version is running incorrectly, and the first test case is any one of the at least one test case; and a version rollback operation is performed on the business platform of the current version.

In one embodiment, the processing module 41 is further configured to detect an exception type corresponding to the verification failure;

If the exception type is a preset type, the step of performing the version rollback operation on the current version of the service platform is triggered, and the preset type includes a null pointer exception or a service exception.

In one embodiment, the processing module 41 is further configured to, if it is detected that the verification of the online business platform by the first test case fails, determine whether the abnormality type corresponding to the failed verification is of the business platform. The sub-module is abnormal or the log is abnormal; if it is determined that the abnormal type corresponding to the failed verification is the sub-module abnormal or the log is abnormal, alarm information is output.

It should be noted that the functions of each functional module of the verification device of the service platform described in the embodiment of the present application may be specifically implemented according to the method in the method embodiment described in FIG. 2 or FIG. 3 , and the specific implementation process may refer to FIG. 2 Or the relevant description of the method embodiment of FIG. 3 is not repeated here.

In the embodiment of the present application, when the communication module 40 receives a data access request sent by the business platform after going online, the processing module 41 may determine the data access request carried in the data access request from at least two preset databases based on preset selection rules. The domain name matches the target database, and the data operation corresponding to the data access request is performed through the target database. For data access based on different domain names, different target databases can be used to perform data operations, so as to efficiently verify the online business platform.

Referring to FIG. 5 , FIG. 5 is a schematic block diagram of a server provided by an embodiment of the present application. As shown in FIG. 5 , the server includes a processor 501 , a memory 502 , and a network interface 503 . The above-mentioned processor 501, memory 502, and network interface 503 may be connected through a bus or in other manners. In FIG. 5 shown in the embodiment of the present application, the connection through a bus is taken as an example. The network interface 503 is controlled by the processor to send and receive messages, the memory 502 is used to store computer programs, the computer programs include program instructions, and the processor 501 is used to execute the program instructions stored in the memory 502 . The processor 501 is configured to invoke the program instruction to execute: receive, through the network interface 503, a data access request carrying a domain name sent by the business platform after going online, where the domain name includes a verification domain name or a production domain name, the The verification domain name is used for the first user to verify the business platform in the production environment, and the production domain name is used for the second user to access the business platform in the production environment; Suppose that a target database matching the domain name is determined in the database; the data operation corresponding to the data access request is performed through the target database, and the data operation includes data query and/or data writing.

In one embodiment, the at least two preset databases include a production database and a verification database, and the processor 501 is specifically configured to, if it is detected that the domain name carried in the data access request is a verification domain name, carry the data access request with The verification token is compared with the preset verification token under the verification domain name; if it is found that the verification token matches the preset verification token, the verification database is determined from at least two preset databases as The verification domain name matches the target database.

In one embodiment, the processor 501 is further configured to determine, from at least two preset databases, a production database as being consistent with the verification token if the verification token does not match the preset verification token by comparison. The target database for domain name matching.

In one embodiment, the at least two preset databases include a production database and a verification database, and the processor 501 is specifically configured to, if it is detected that the domain name carried in the data access request is a production domain name, select from the at least two preset databases The production database is determined as the target database matching the production domain name.

In one embodiment, the processor 501 is further configured to verify the online business platform through at least one test case in a production environment; if it is detected that the first test case has not verified the online business platform If the test is passed, it is determined that the business platform of the current version is running incorrectly, and the first test case is any one of the at least one test case; and a version rollback operation is performed on the business platform of the current version.

In one embodiment, the processor 501 is further configured to detect an exception type corresponding to the verification failure;

If the exception type is a preset type, the step of performing the version rollback operation on the current version of the service platform is triggered, and the preset type includes a null pointer exception or a service exception.

In one embodiment, the processor 501 is further configured to, if it is detected that the verification of the online business platform by the first test case fails, determine whether the abnormality type corresponding to the failed verification is of the business platform. The sub-module is abnormal or the log is abnormal; if it is determined that the abnormal type corresponding to the failed verification is the sub-module abnormal or the log is abnormal, alarm information is output.

It should be understood that, in this embodiment of the present application, the processor 501 may be a central processing unit (Central Processing Unit, CPU), and the processor 501 may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 502 may include read only memory and random access memory, and provides instructions and data to the processor 501 . A portion of memory 502 may also include non-volatile random access memory. For example, memory 502 may also store device type information.

In specific implementation, the processor 501, the memory 502, and the network interface 503 described in the embodiments of the present application may perform the implementations described in the method embodiments described in FIG. 2 or FIG. 3 provided in the embodiments of the present application, and may also perform The implementation manner of the verification device of the service platform described in the embodiment of the present application will not be repeated here.

In this embodiment of the present application, when the network interface 503 receives a data access request sent by the business platform after going online, the processor 501 may determine the data access request carried in the data access request from at least two preset databases based on a preset selection rule. The domain name matches the target database, and the data operation corresponding to the data access request is performed through the target database. For data access based on different domain names, different target databases can be used to perform data operations, so as to efficiently verify the online business platform.

In another embodiment of the present invention, a computer-readable storage medium is provided, where a computer program is stored in the computer-readable storage medium, and the computer program includes program instructions, and when the program instructions are executed by a processor, realize: receiving A data access request carrying a domain name sent by the business platform after going online, the domain name includes a verification domain name or a production domain name, and the verification domain name is used for the first user to verify the business platform in a production environment, the The production domain name is used for the second user to access the business platform in the production environment; a target database matching the domain name is determined from at least two preset databases based on preset selection rules; The data operation corresponding to the data access request, where the data operation includes data query and/or data writing.

The computer-readable storage medium may be an internal storage unit of the server described in any of the foregoing embodiments, such as a hard disk or a memory of the server. The computer-readable storage medium may also be an external storage device of the server, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), and a secure digital (Secure Digital, SD) card equipped on the server. , Flash card (Flash Card) and so on. Further, the computer-readable storage medium may also include both an internal storage unit of the server and an external storage device. The computer-readable storage medium is used to store the computer program and other programs and data required by the server. The computer-readable storage medium can also be used to temporarily store data that has been or will be output.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium. During execution, the processes of the embodiments of the above-mentioned methods may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM) or the like.

The above disclosures are only part of the embodiments of the present invention, and of course, the scope of the rights of the present invention cannot be limited by this. Those of ordinary skill in the art can understand all or part of the procedures for realizing the above embodiments, and make according to the claims of the present invention. The equivalent changes of the invention still belong to the scope covered by the invention.

Claims (10)

1. A method for verifying a service platform, the method comprising:

receiving a data access request carrying a domain name sent by the service platform after the service platform is online, wherein the domain name comprises a verification domain name or a production domain name, the verification domain name is used for a first user to verify the service platform in a production environment, and the production domain name is used for a second user to access the service platform in the production environment;

determining a target database matched with the domain name from at least two preset databases based on a preset selection rule;

and executing data operation corresponding to the data access request through the target database, wherein the data operation comprises data query and/or data write.

2. The method according to claim 1, wherein the at least two predetermined databases include a production database and a verification database, and the determining a target database matching the domain name from the at least two predetermined databases based on a predetermined database selection rule comprises:

if the domain name carried in the data access request is detected to be the verification domain name, comparing the verification token carried in the data access request with a preset verification token under the verification domain name;

and if the verification token is matched with the preset verification token after comparison, determining a verification database as a target database matched with the verification domain name from at least two preset databases.

3. The method according to claim 2, wherein after comparing the authentication token carried by the data access request with a preset authentication token under an authentication domain name, the method further comprises:

and if the verification token is not matched with the preset verification token after comparison, determining a production database as a target database matched with the verification domain name from at least two preset databases.

4. The method according to claim 1, wherein the at least two predetermined databases include a production database and a verification database, and the determining a target database matching the domain name from the at least two predetermined databases based on a predetermined database selection rule comprises:

and if the domain name carried in the data access request is detected to be the production domain name, determining the production database as a target database matched with the production domain name from at least two preset databases.

5. The method of claim 1, further comprising:

verifying the service platform after the service platform is on line in a production environment through at least one test case;

if the verification of a first test case on the online service platform is not passed, determining that the service platform of the current version is in error in operation, wherein the first test case is any one of the at least one test case;

and executing the rollback operation of the version of the service platform of the current version.

6. The method of claim 5, wherein before performing a version rollback operation on the current version of the service platform, the method further comprises:

detecting the corresponding abnormal type of which the verification fails;

and if the exception type is a preset type, triggering and executing the step of executing the version rollback operation on the service platform of the current version, wherein the preset type comprises null pointer exception or service exception.

7. The method of claim 5, further comprising:

if the first test case is detected to fail to verify the online service platform, determining whether the abnormal type corresponding to the failed verification is the sub-module abnormality or log abnormality of the service platform;

and if the abnormal type corresponding to the failed verification is determined to be the sub-module abnormality or the log abnormality, outputting alarm information.

8. An apparatus for validating a service platform, the apparatus comprising:

the communication module is used for receiving a data access request which is sent by the service platform after the service platform is on line and carries a domain name, wherein the domain name comprises a verification domain name or a production domain name, the verification domain name is used for a first user to verify the service platform in a production environment, and the production domain name is used for a second user to access the service platform in the production environment;

the processing module is used for determining a target database matched with the domain name from at least two preset databases based on a preset selection rule;

the processing module is further configured to execute a data operation corresponding to the data access request through the target database, where the data operation includes query of data and/or write-in of data.

9. A server, comprising a processor and a memory, the processor and the memory being interconnected, wherein the memory is configured to store a computer program comprising program instructions, and wherein the processor is configured to invoke the program instructions to perform the method of any one of claims 1-7.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, which is executed by a processor to implement the method of any one of claims 1-7.

Images