CN110442395B - Method and device for releasing product configuration data, front-end server and back-end server - Google Patents
Method and device for releasing product configuration data, front-end server and back-end server Download PDFInfo
- Publication number
- CN110442395B CN110442395B CN201910689537.6A CN201910689537A CN110442395B CN 110442395 B CN110442395 B CN 110442395B CN 201910689537 A CN201910689537 A CN 201910689537A CN 110442395 B CN110442395 B CN 110442395B
- Authority
- CN
- China
- Prior art keywords
- configuration data
- product configuration
- environment
- product
- end server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application is applicable to the field of computers, and provides a method and a device for issuing product configuration data, a front-end server and a back-end server. The method comprises the following steps: the back-end server carries out maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation; the back-end server packages the product configuration data after the maintenance operation into a format which can be directly called by the front-end server to obtain the packaged product configuration data; the back-end server issues the packaged product configuration data to a cache; polling a latest version of product release notice from a rear-end server by a front-end server at intervals of preset time to obtain a latest version number; and the front-end server calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number. The method and the device can break through the performance bottleneck of the internet insurance era in the high concurrent user insurance investment.
Description
Technical Field
The present application belongs to the field of computers, and in particular, to a method and an apparatus for issuing product configuration data, a front-end server, and a back-end server.
Background
When the backend server performs any operations such as adding, deleting, modifying, and querying on basic data or configuration data such as rules of a product, and then issues the product configuration data to the front end, the prior art calls the product configuration data of the backend server by using an API interface. However, the mode that the front-end server calls the product configuration data of the back-end server by using the API interface cannot solve the performance bottleneck problem in the internet insurance era of high concurrent user insurance.
Disclosure of Invention
The application aims to provide a method and a device for releasing product configuration data, a computer readable storage medium, a front-end server and a back-end server, and aims to solve the problem that performance bottlenecks cannot be solved in the internet insurance era with high concurrent user insurance in a mode that the front-end server calls the product configuration data of the back-end server by using an API (application program interface).
In a first aspect, the present application provides a method for publishing product configuration data, the method including:
the back-end server carries out maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation;
the back-end server packages the product configuration data after the maintenance operation into a format which can be directly called by the front-end server to obtain the packaged product configuration data;
the back-end server issues the packaged product configuration data to a cache;
polling a latest version of product release notice from a rear-end server by a front-end server at intervals of preset time to obtain a latest version number;
and the front-end server calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number.
Further, after the back-end server performs maintenance operation on the product configuration data and obtains the product configuration data after the maintenance operation, the method for issuing the product configuration data further includes:
and after receiving the synchronization instruction, synchronizing the product configuration data after the maintenance operation to all different environments in the back-end server.
In a second aspect, the present application provides a system for publishing product configuration data, the system comprising a backend server and a backend server, wherein:
the back-end server carries out maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation;
the back-end server packages the product configuration data after the maintenance operation into a format which can be directly called by the front-end server to obtain the packaged product configuration data;
the back-end server issues the packaged product configuration data to a cache;
polling a latest version of product release notice from a rear-end server by a front-end server at intervals of preset time to obtain a latest version number;
and the front-end server calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number.
In a third aspect, the present application provides a method for publishing product configuration data, where the method includes:
performing maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation;
packaging the product configuration data after maintenance operation into a format which can be directly called by a front-end server to obtain the packaged product configuration data;
and releasing the packaged product configuration data to a cache so that a front-end server polls a rear-end server for a latest version of product release notice at preset time intervals to obtain a latest version number, and calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number.
In a fourth aspect, the present application provides an apparatus for publishing product configuration data, the apparatus being embedded in a backend server, the apparatus comprising:
the maintenance module is used for performing maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation;
the packaging module is used for packaging the product configuration data after the maintenance operation into a format which can be directly called by the front-end server to obtain the packaged product configuration data;
and the release module is used for releasing the packaged product configuration data to a cache so that the front-end server polls the rear-end server for a latest version of product release notice at preset time intervals to obtain a latest version number, and calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number.
In a fifth aspect, the present application provides a computer-readable storage medium storing a computer program, wherein the computer program is configured to, when executed by a processor, implement the steps of the method for distributing product configuration data according to the third aspect.
In a sixth aspect, the present application provides a backend server, comprising:
one or more processors;
a memory; and
one or more computer programs, the processor and the memory being connected by a bus, wherein the one or more computer programs are stored in the memory and configured to be executed by the one or more processors, which when executing the computer programs implement the steps of the method of distribution of product configuration data according to the third aspect.
In the method for issuing the product configuration data, the back-end server encapsulates the product configuration data after maintenance operation into a format which can be directly called by the front-end server, and issues the encapsulated product configuration data to the cache; and the front-end server polls the rear-end server for the latest version of the product release notice at preset time intervals to obtain the latest version number, and calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number. Therefore, the performance bottleneck of the internet insurance era in the high concurrent user insurance time can be broken through;
in addition, since the back-end server performs the maintenance operation on the product configuration data, after the product configuration data after the maintenance operation is obtained, the method for issuing the product configuration data further includes: and after receiving the synchronization instruction, synchronizing the product configuration data after the maintenance operation to all different environments in the back-end server. Therefore, compared with the existing problem that an operator needs to operate for many times when data synchronization in different environments on the market mainly uses Excel uploaded data or uses synchronous software CDC and the like, the consistency of all environment data cannot be guaranteed when basic configuration is needed to be modified when BUG occurs, the method and the device can enable product configuration data to be maintained in different environments in a unified mode, and the accuracy and the integrity of the product configuration data are guaranteed.
Drawings
Fig. 1 is a flowchart of a method for publishing product configuration data according to an embodiment of the present application.
Fig. 2 is a schematic diagram of a publishing configuration interface in an embodiment of the present application.
Fig. 3 is a schematic diagram of a release configuration information list in an embodiment of the present application.
Fig. 4 is a schematic diagram of a comparison interface showing release configuration information and a version to be released and an online validation version in an embodiment of the present application.
FIG. 5 is a schematic diagram of a configuration history page in an embodiment of the present application.
Fig. 6 is a schematic diagram of a synchronous operation interface in an embodiment of the present application.
Fig. 7 is a flowchart illustrating synchronization from a DEV environment to a SIT environment, from the SIT environment to a UAT environment, and from the UAT environment to a PRD environment according to an embodiment of the present application.
Fig. 8 is a schematic diagram of a system for publishing product configuration data according to an embodiment of the present application.
Fig. 9 is a block diagram of an apparatus for issuing product configuration data according to an embodiment of the present application.
Fig. 10 is a block diagram illustrating a specific structure of a backend server according to an embodiment of the present application.
Detailed Description
In order to make the purpose, technical solution and beneficial effects of the present application more clear and more obvious, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
Referring to fig. 1, a method for publishing product configuration data according to an embodiment of the present application includes the following steps: it should be noted that, if the result is substantially the same, the method for issuing the product configuration data in the present application is not limited to the flow sequence shown in fig. 1.
S101, the back-end server carries out maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation.
In one embodiment of the present application, the product configuration data includes basic data or rules of the product, such as application rules, claim rules, renewal rules, configuration of wind control, guarantee plan documents, business numbers, risk categories, responsibilities, terms, rate tables, and the like. Maintenance operations include add, delete, modify, query, etc.
S102, the back-end server packages the product configuration data after the maintenance operation into a format which can be directly called by the front-end server, and the packaged product configuration data is obtained.
In an embodiment of the present application, the formats that can be directly called by the front-end server include Json, xml, yaml, protobuffer, and the like.
S102 may specifically be:
and the back-end server packages the product configuration data into a format which can be directly called by the front-end server with the marked version number to obtain the packaged product configuration data with the marked version number.
The product configuration data may be product configuration data of a plurality of different environments, such as product configuration data of a Development (DEV) environment, product configuration data of a System Integration Test (SIT) environment, product configuration data of a User Acceptance Test (UAT) environment or product configuration data of a Product (PRD) environment.
In an embodiment of the present application, after S102, the method may further include:
the back-end server generates release configuration information according to the product configuration data after the maintenance operation; the release configuration information comprises a type code, a type name, a version number, a publisher, a release type (such as a product and an insurance application rule, a guarantee plan file, a renewal rule, a merchant number and the like), a change type, a release state, time and the like;
receiving one or more items of information in the release configuration information input by a maintenance person on a release configuration interface (shown in FIG. 2) of a release plan as a query keyword;
inquiring a related publishing configuration information list according to the inquiry keywords (as shown in figure 3);
after receiving the viewing instruction, displaying the comparison between the release configuration information and the to-be-released version and the online effective version, providing a release button, and also providing a peripheral verification button (as shown in fig. 4);
when receiving a distribution instruction sent by a distribution button, verifying the product configuration data after the maintenance operation to be distributed, and prompting a verification result, if the verification is correct, executing S103, wherein the verification of the product configuration data after the maintenance operation to be distributed specifically includes verifying the correctness and integrity of the product configuration data after the maintenance operation to be distributed, and also can verify a peripheral system of the product configuration data after the maintenance operation to be distributed, such as a commission configuration system.
When the peripheral verification button is provided, the following steps may be further included: and when a verification instruction sent by the peripheral verification button is received, verifying peripheral systems, such as commission configuration systems, of the product configuration data after the maintenance operation to be issued.
And when the back-end server generates release configuration information according to the product configuration data after the maintenance operation, the back-end server also forms a version tree according to the version number, and performs version comparison and rollback on the basis of the version tree so as to ensure the safety and reliability of the release action.
After the backend server generates the release configuration information according to the product configuration data after the maintenance operation, the method may further include:
receiving an instruction of entering a configuration history page; specifically, the method includes receiving an instruction for entering a configuration history page on a release configuration interface;
all versions of the product configuration data are presented on the configuration history page, and the configuration personnel can select any two versions for comparison (as shown in FIG. 5).
S103, the back-end server issues the packaged product configuration data to a cache.
In an embodiment of the present application, S103 may specifically be:
and the back-end server issues the packaged product configuration data to a redis cache.
The issue refers to issuing product configuration data between different platforms in the same environment, for example, product configuration data is issued from a back-end server in the DEV environment to a front-end server in the DEV environment, product configuration data is issued from a back-end server in the SIT environment to a front-end server in the SIT environment, product configuration data is issued from a back-end server in the UAT environment to a front-end server in the UAT environment, product configuration data is issued from a back-end server in the PRD environment to a front-end server in the PRD environment, and the like.
In an embodiment of the present application, S103 may specifically include the following steps:
the method comprises the steps that a back-end server generates a latest version of product release notice, wherein the latest version of product release notice comprises a latest version number;
the back-end server compares versions corresponding to the product configuration data in the cache;
and when the version in the latest version of the product release notice is judged to be a new version, releasing the packaged product configuration data to the cache, thereby realizing hot update of the product configuration data.
And S104, the front-end server polls the rear-end server for the latest version of the product release notice at preset time intervals to acquire the latest version number.
And S105, calling the packaged product configuration data corresponding to the latest version number from the cache by the front-end server according to the latest version number.
In an embodiment of the present application, after S101, the method for issuing product configuration data may further include the following steps:
after receiving the synchronization instruction, synchronizing the product configuration data after the maintenance operation to all different environments in the back-end server; for example, the DEV environment is synchronized to the SIT environment, the SIT environment is synchronized to the UAT environment, and the UAT environment is synchronized to the PRD environment, so that the product configuration data does not need to be maintained in multiple copies in different environments, the efficiency is optimized, and the data accuracy is improved.
The synchronization command is generated by clicking a synchronization button. (as shown in FIG. 6)
Referring to fig. 7, the synchronization from the DEV environment to the SIT environment, the SIT environment to the UAT environment, and the UAT environment to the PRD environment includes the following steps:
inputting model information of a product in a DEV environment, wherein the model information of the product specifically comprises basic data and rules of the product, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to an SIT environment if the test passes;
in the SIT environment, inputting relevant information of the SIT environment, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to the UAT environment if the test passes;
in the UAT environment, inputting relevant information of the UAT environment, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to a PRD environment if the test passes;
and under the PRD environment, recording relevant information of the PRD environment, checking a release plan, executing release, executing a test, and ending the synchronous flow if the test is passed.
Therefore, relevant information of the online product can be efficiently and transparently circulated in different environments, all links work in series, the life cycle of the product from absence to existence and from establishment to online is clearly shown, the data can provide basic data for product decision after being duralized, and the data can be used for counteracting the optimization process after being quantized.
The method for releasing the product configuration data provided by the embodiment of the application can be applied to internet insurance products or internet financial products and the like.
Referring to fig. 8, an embodiment of the present application provides a system for publishing product configuration data, where the system includes a back-end server 11 and a front-end server 12, and the back-end server 11 and the front-end server 12 are configured to execute the steps of the method for publishing product configuration data provided in the embodiment of the present application. The specific implementation process is detailed in the whole specification, and is not described in detail herein.
Referring to fig. 9, an embodiment of the present application provides an apparatus for publishing product configuration data, where the apparatus is built in a backend server, and the apparatus includes:
the maintenance module 21 is configured to perform maintenance operation on the product configuration data to obtain product configuration data after the maintenance operation;
the packaging module 22 is configured to package the product configuration data after the maintenance operation into a format that can be directly called by the front-end server, so as to obtain the packaged product configuration data;
the publishing module 23 is configured to publish the packaged product configuration data to the cache, so that the front-end server polls the back-end server for a product publishing notification of a latest version at preset time intervals to obtain a latest version number, and calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number.
The device and the method for issuing the product configuration data provided in the embodiment of the present application belong to the same concept, and the specific implementation process is detailed in the entire specification, which is not described herein again.
An embodiment of the present application provides a computer-readable storage medium, which stores a computer program, which when executed by a processor, implements the steps of:
performing maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation;
packaging the product configuration data after the maintenance operation into a format which can be directly called by a front-end server to obtain the packaged product configuration data;
and releasing the packaged product configuration data to a cache so that a front-end server polls a rear-end server for a latest version of product release notice at preset time intervals to obtain a latest version number, and calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number.
In an embodiment of the present application, the formats that can be directly called by the front-end server include Json, xml, yaml, and Protobuffer.
The method for packaging the product configuration data after the maintenance operation into a format that can be directly called by a front-end server comprises the following steps:
and packaging the product configuration data into a format which can be directly called by the front-end server with the marked version number to obtain the packaged product configuration data with the marked version number.
The issuing of the packaged product configuration data to the cache specifically includes:
and issuing the packaged product configuration data to a redis cache.
The issuing of the packaged product configuration data to the cache specifically includes:
generating a product release notice of the latest version;
comparing versions corresponding to the product configuration data in the cache;
and when the version in the latest version of the product release notice is judged to be a new version, releasing the packaged product configuration data to the cache.
After the maintenance operation is carried out on the product configuration data to obtain the product configuration data after the maintenance operation, the following steps are also executed:
and after receiving the synchronization instruction, synchronizing the product configuration data after the maintenance operation to all different environments in the back-end server.
The step of synchronizing the product configuration data after the maintenance operation to all different environments in the back-end server specifically includes:
synchronizing the product configuration data after the maintenance operation from the DEV environment to the SIT environment, then synchronizing from the SIT environment to the UAT environment, and then synchronizing from the UAT environment to the PRD environment.
The synchronizing the product configuration data after the maintenance operation from the DEV environment to the SIT environment, then from the SIT environment to the UAT environment, and then from the UAT environment to the PRD environment specifically includes:
in a DEV environment, inputting model information of a product, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to an SIT environment if the test passes;
in the SIT environment, inputting relevant information of the SIT environment, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to the UAT environment if the test passes;
in the UAT environment, inputting relevant information of the UAT environment, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to a PRD environment if the test passes;
and under the PRD environment, recording relevant information of the PRD environment, checking a release plan, executing release, executing a test, and ending the synchronous flow if the test is passed.
Fig. 10 shows a specific structural block diagram of a back-end server provided in an embodiment of the present application, where a back-end server 100 includes: one or more processors 101, a memory 102, and one or more computer programs, wherein the processors 101 and the memory 102 are connected by a bus, the one or more computer programs being stored in the memory 102 and configured to be executed by the one or more processors 101, the computer programs, when executed by the processors 101, implementing the steps as described below.
Performing maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation;
packaging the product configuration data after the maintenance operation into a format which can be directly called by a front-end server to obtain the packaged product configuration data;
and releasing the packaged product configuration data to a cache so that a front-end server polls a rear-end server for a latest version of product release notice at preset time intervals to obtain a latest version number, and calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number.
In an embodiment of the present application, the formats that the front-end server can directly call include Json, xml, yaml, and Protobuffer.
The packaging of the product configuration data after the maintenance operation into a format that can be directly called by the front-end server, and the specific steps of obtaining the packaged product configuration data are as follows:
and packaging the product configuration data into a format which can be directly called by the front-end server with the marked version number to obtain the packaged product configuration data with the marked version number.
The issuing of the packaged product configuration data to the cache specifically includes:
and issuing the packaged product configuration data to a redis cache.
The issuing of the packaged product configuration data to the cache specifically includes:
generating a product release notice of the latest version;
comparing versions corresponding to the product configuration data in the cache;
and when the version in the latest version of the product release notice is judged to be a new version, releasing the packaged product configuration data to the cache.
After the maintenance operation is carried out on the product configuration data to obtain the product configuration data after the maintenance operation, the following steps are also executed:
and after receiving the synchronization instruction, synchronizing the product configuration data after the maintenance operation to all different environments in the back-end server.
The step of synchronizing the product configuration data after the maintenance operation to all different environments in the back-end server specifically includes:
synchronizing the product configuration data after the maintenance operation from the DEV environment to the SIT environment, then synchronizing from the SIT environment to the UAT environment, and then synchronizing from the UAT environment to the PRD environment.
The synchronizing the product configuration data after the maintenance operation from the DEV environment to the SIT environment, then from the SIT environment to the UAT environment, and then from the UAT environment to the PRD environment specifically includes:
in a DEV environment, inputting model information of a product, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to an SIT environment if the test passes;
in the SIT environment, inputting relevant information of the SIT environment, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to the UAT environment if the test passes;
under the UAT environment, inputting relevant information of the UAT environment, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to a PRD environment if the test is passed;
and under the PRD environment, recording related information of the PRD environment, checking a release plan, executing release, executing a test, and ending the synchronous flow if the test is passed.
In the method for issuing the product configuration data, the back-end server encapsulates the product configuration data after maintenance operation into a format which can be directly called by the front-end server, and issues the encapsulated product configuration data to the cache; and the front-end server polls the rear-end server for the latest version of the product release notice at preset time intervals to obtain the latest version number, and calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number. Therefore, the performance bottleneck of the internet insurance era in the high concurrent user insurance time can be broken through;
in addition, since the back-end server performs the maintenance operation on the product configuration data, after the product configuration data after the maintenance operation is obtained, the method for issuing the product configuration data further includes: and after receiving the synchronization instruction, synchronizing the product configuration data after the maintenance operation to all different environments in the back-end server. Therefore, compared with the existing problem that an operator needs to operate for many times when data synchronization of different environments in the market mainly uses Excel uploaded data or uses synchronization software CDC and the like, the consistency of each environment data cannot be guaranteed when the BUG needs to be modified and basic configuration occurs, the method and the device can enable product configuration data to be maintained in different environments in a unified mode, and the accuracy and the integrity of the product configuration data are guaranteed.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by hardware related to instructions of a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: read Only Memory (ROM), random Access Memory (RAM), magnetic or optical disks, and the like.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (34)
1. A method for issuing product configuration data, which is applied to an internet insurance product or an internet financial product, the method comprising:
the back-end server carries out maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation, wherein the product configuration data comprises basic data or rules of the product;
the back-end server packages the product configuration data after the maintenance operation into a format which can be directly called by the front-end server to obtain the packaged product configuration data;
the back-end server issues the packaged product configuration data to a cache;
polling a latest version of product release notice from a rear-end server by a front-end server at intervals of preset time to obtain a latest version number;
and the front-end server calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number.
2. The method of claim 1, wherein the maintenance operation comprises one or any combination of an addition, a deletion, a modification, a query.
3. The method of claim 1, wherein the formats that the front-end server can directly call include Json, xml, yaml, and Protobuffer.
4. The method of claim 1, wherein the backend server encapsulates the product configuration data after the maintenance operation into a format that can be directly invoked by the frontend server, and the obtaining of the encapsulated product configuration data specifically includes:
and the back-end server packages the product configuration data into a format which can be directly called by the front-end server with the marked version number to obtain the packaged product configuration data with the marked version number.
5. The method of claim 1, wherein the product configuration data is product configuration data for a plurality of different environments.
6. The method of claim 5, wherein the product configuration data is product configuration data of a development environment, product configuration data of a system-internal integrated test environment, product configuration data of a user acceptance test environment, or product configuration data of a product environment.
7. The method of claim 1, wherein the back-end server encapsulates the product configuration data after the maintenance operation into a format directly invokable by the front-end server, and after obtaining the encapsulated product configuration data, the method further comprises:
the back-end server generates release configuration information according to the product configuration data after the maintenance operation;
receiving one or more items of information in the release configuration information input by maintenance personnel on a release configuration interface of a release plan as query keywords;
inquiring a related release configuration information list according to the inquiry keywords;
after receiving the checking instruction, displaying the comparison between the release configuration information and the version to be released and the online effective version, and providing a release button;
when receiving a release instruction sent by a release button, verifying the product configuration data after the maintenance operation to be released, prompting a verification result, and if the verification is correct, executing the step that the back-end server releases the packaged product configuration data to the cache.
8. The method according to claim 7, wherein the verifying the product configuration data after the maintenance operation to be distributed specifically includes verifying correctness and integrity of the product configuration data after the maintenance operation to be distributed, and also verifying a peripheral system of the product configuration data after the maintenance operation to be distributed.
9. The method of claim 7, wherein when the backend server generates the release configuration information according to the product configuration data after the maintenance operation, the backend server further constructs a version tree according to the version number, and performs version comparison and rollback based on the version tree.
10. The method of claim 9, wherein after the back-end server generates release configuration information from the product configuration data after the maintenance operation, the method further comprises:
receiving an instruction of entering a configuration history page;
all versions of the product configuration data are displayed on a configuration history page for a configuration person to select any two versions for comparison.
11. The method of claim 1, wherein the publishing, by the backend server, the encapsulated product configuration data to the cache is specifically:
and the back-end server issues the packaged product configuration data to a redis cache.
12. The method of claim 1 or 11, wherein the publishing, by the backend server, the encapsulated product configuration data to the cache specifically comprises:
the back-end server generates a latest version of product release notice, wherein the latest version of product release notice comprises a latest version number;
the back-end server compares versions corresponding to the product configuration data in the cache;
and when the version in the latest version of the product release notice is judged to be a new version, releasing the packaged product configuration data to the cache.
13. The method of claim 1, wherein the back-end server performs a maintenance operation on the product configuration data, and after obtaining the product configuration data after the maintenance operation, the method for publishing the product configuration data further comprises:
and after receiving the synchronization instruction, synchronizing the product configuration data after the maintenance operation to all different environments in the back-end server.
14. The method of claim 13, wherein synchronizing the product configuration data after the maintenance operation to all of the different environments in the back-end server is specifically:
synchronizing the product configuration data after the maintenance operation from the DEV environment to the SIT environment, then synchronizing from the SIT environment to the UAT environment, and then synchronizing from the UAT environment to the PRD environment.
15. The method as claimed in claim 14, wherein the synchronizing the product configuration data after the maintenance operation from the DEV environment to the SIT environment, then from the SIT environment to the UAT environment, and then from the UAT environment to the PRD environment specifically comprises:
in a DEV environment, inputting model information of a product, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to an SIT environment if the test passes;
in the SIT environment, inputting relevant information of the SIT environment, checking a release plan, executing release, executing a test, and synchronizing model information of a product to the UAT environment if the test passes;
in the UAT environment, inputting relevant information of the UAT environment, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to a PRD environment if the test passes;
and under the PRD environment, recording relevant information of the PRD environment, checking a release plan, executing release, executing a test, and ending the synchronous flow if the test is passed.
16. A system for issuing product configuration data, the system being applied to an internet insurance product or an internet financial product, the system comprising a backend server and a backend server, wherein:
the back-end server carries out maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation, wherein the product configuration data comprises basic data or rules of the product;
the back-end server packages the product configuration data after the maintenance operation into a format which can be directly called by the front-end server to obtain the packaged product configuration data;
the back-end server issues the packaged product configuration data to a cache;
polling a latest version of product release notice from a rear-end server by a front-end server at intervals of preset time to obtain a latest version number;
and the front-end server calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number.
17. The system of claim 16, wherein the back-end server encapsulates the product configuration data after the maintenance operation into a format directly invokable by the front-end server, and the obtaining of the encapsulated product configuration data specifically includes:
and the back-end server packages the product configuration data into a format which can be directly called by the front-end server with the marked version number to obtain the packaged product configuration data with the marked version number.
18. The system of claim 16, wherein the back-end server encapsulates the product configuration data after the maintenance operation into a format directly invokable by the front-end server, and after obtaining the encapsulated product configuration data, the back-end server further performs the steps of:
the back-end server generates release configuration information according to the product configuration data after the maintenance operation;
receiving one or more items of information in the release configuration information input by maintenance personnel on a release configuration interface of a release plan as query keywords;
inquiring a related release configuration information list according to the inquiry keywords;
after receiving the checking instruction, displaying the comparison between the release configuration information and the version to be released and the online effective version, and providing a release button;
when receiving a release instruction sent by a release button, verifying the product configuration data after the maintenance operation to be released, prompting a verification result, and if the verification is correct, executing a step of releasing the packaged product configuration data to a cache by the back-end server.
19. The system of claim 16, wherein the publishing of the encapsulated product configuration data to the cache by the backend server is specifically:
and the back-end server issues the packaged product configuration data to a redis cache.
20. The system of claim 16 or 19, wherein the backend server publishing the encapsulated product configuration data to the cache specifically comprises:
the back-end server generates a latest version of product release notice, wherein the latest version of product release notice comprises a latest version number;
the back-end server compares the versions corresponding to the product configuration data in the cache;
and when the version in the latest version of the product release notice is judged to be a new version, releasing the packaged product configuration data to the cache.
21. The system of claim 16, wherein the backend server performs a maintenance operation on the product configuration data, and after obtaining the product configuration data after the maintenance operation, the backend server further performs the following steps:
and after receiving the synchronization instruction, synchronizing the product configuration data after the maintenance operation to all different environments in the back-end server.
22. The system of claim 21, wherein the synchronizing the product configuration data after the maintenance operation to all of the different environments in the back-end server is specifically:
synchronizing the product configuration data after the maintenance operation from the DEV environment to the SIT environment, then synchronizing from the SIT environment to the UAT environment, and then synchronizing from the UAT environment to the PRD environment.
23. The system of claim 22, wherein synchronizing the product configuration data after the maintenance operation from the DEV environment to the SIT environment, then from the SIT environment to the UAT environment, then from the UAT environment to the PRD environment specifically comprises:
in a DEV environment, inputting model information of a product, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to an SIT environment if the test passes;
in the SIT environment, inputting relevant information of the SIT environment, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to the UAT environment if the test passes;
in the UAT environment, inputting relevant information of the UAT environment, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to a PRD environment if the test passes;
and under the PRD environment, recording relevant information of the PRD environment, checking a release plan, executing release, executing a test, and ending the synchronous flow if the test is passed.
24. A method for issuing product configuration data, which is applied to an internet insurance product or an internet financial product, the method comprising:
performing maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation;
packaging the product configuration data after the maintenance operation into a format which can be directly called by a front-end server to obtain the packaged product configuration data, wherein the product configuration data comprises basic data or rules of the product;
and releasing the packaged product configuration data to a cache so that a front-end server polls a rear-end server for a latest version of product release notice at preset time intervals to obtain a latest version number, and calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number.
25. The method of claim 24, wherein the formats directly invokable by the front-end server include Json, xml, yaml, and Protobuffer.
26. The method according to claim 24, wherein the encapsulating the product configuration data after the maintenance operation into a format directly invokable by the front-end server, and the obtaining of the encapsulated product configuration data specifically includes:
and packaging the product configuration data into a format which can be directly called by the front-end server with the marked version number to obtain the packaged product configuration data with the marked version number.
27. The method of claim 24, wherein publishing the encapsulated product configuration data to a cache specifically includes:
and issuing the packaged product configuration data to a redis cache.
28. The method of claim 24 or 27, wherein publishing the encapsulated product configuration data to a cache specifically comprises:
generating a product release notice of the latest version;
comparing versions corresponding to the product configuration data in the cache;
and when the version in the latest version of the product release notice is judged to be a new version, releasing the packaged product configuration data to the cache.
29. The method of claim 24, wherein after performing the maintenance operation on the product configuration data and obtaining the product configuration data after the maintenance operation, the method further comprises:
and after receiving the synchronization instruction, synchronizing the product configuration data after the maintenance operation to all different environments in the back-end server.
30. The method of claim 29, wherein synchronizing the product configuration data after the maintenance operation to all of the different environments in the back-end server is specifically:
synchronizing the product configuration data after the maintenance operation from the DEV environment to the SIT environment, then synchronizing from the SIT environment to the UAT environment, and then synchronizing from the UAT environment to the PRD environment.
31. The method as claimed in claim 30, wherein the synchronizing the product configuration data after the maintenance operation from the DEV environment to the SIT environment, then from the SIT environment to the UAT environment, and then from the UAT environment to the PRD environment comprises:
in a DEV environment, inputting model information of a product, checking a publishing plan, executing publishing, executing a test, and synchronizing the model information of the product to an SIT environment if the test passes;
in the SIT environment, inputting relevant information of the SIT environment, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to the UAT environment if the test passes;
in the UAT environment, inputting relevant information of the UAT environment, checking a release plan, executing release, executing a test, and synchronizing the model information of the product to a PRD environment if the test passes;
and under the PRD environment, recording relevant information of the PRD environment, checking a release plan, executing release, executing a test, and ending the synchronous flow if the test is passed.
32. An apparatus for distributing product configuration data, the apparatus being applied to an internet insurance product or an internet financial product, the apparatus being built in a backend server, the apparatus comprising:
the maintenance module is used for carrying out maintenance operation on the product configuration data to obtain the product configuration data after the maintenance operation, and the product configuration data comprises basic data or rules of the product;
the packaging module is used for packaging the product configuration data after the maintenance operation into a format which can be directly called by the front-end server to obtain the packaged product configuration data;
and the release module is used for releasing the packaged product configuration data to a cache so that the front-end server polls the rear-end server for a latest version of product release notice at preset time intervals to obtain a latest version number, and calls the packaged product configuration data corresponding to the latest version number from the cache according to the latest version number.
33. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method for distribution of product configuration data according to any one of claims 24 to 31.
34. A back-end server, comprising:
one or more processors;
a memory; and
one or more computer programs, the processor and the memory being connected by a bus, wherein the one or more computer programs are stored in the memory and configured to be executed by the one or more processors, characterized in that the steps of the method for distribution of product configuration data according to any of claims 24 to 31 are implemented when the computer programs are executed by the processors.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910689537.6A CN110442395B (en) | 2019-07-29 | 2019-07-29 | Method and device for releasing product configuration data, front-end server and back-end server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910689537.6A CN110442395B (en) | 2019-07-29 | 2019-07-29 | Method and device for releasing product configuration data, front-end server and back-end server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110442395A CN110442395A (en) | 2019-11-12 |
| CN110442395B true CN110442395B (en) | 2023-03-24 |
Family
ID=68431959
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910689537.6A Active CN110442395B (en) | 2019-07-29 | 2019-07-29 | Method and device for releasing product configuration data, front-end server and back-end server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110442395B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111142749B (en) * | 2019-12-19 | 2023-09-22 | 阳光人寿保险股份有限公司 | Insurance product release method, system and terminal equipment |
| CN113778555A (en) * | 2021-09-02 | 2021-12-10 | 百融至信(北京)征信有限公司 | Distributed configuration method and system |
| CN117041044A (en) * | 2023-08-23 | 2023-11-10 | 中电金信软件有限公司 | Gateway configuration method, device and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302895A (en) * | 2015-10-21 | 2016-02-03 | 浪潮通用软件有限公司 | Data caching synchronization method, server and client side |
| CN105786531A (en) * | 2014-12-19 | 2016-07-20 | 江苏融成嘉益信息科技有限公司 | Cooperative work method for online software update and data encryption |
| CN107133234A (en) * | 2016-02-29 | 2017-09-05 | 阿里巴巴集团控股有限公司 | The method of data cached renewal, apparatus and system |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB0214670D0 (en) * | 2002-06-26 | 2002-08-07 | Ibm | Arrangement and method for update of configuration cache data |
| CN103607424B (en) * | 2013-10-24 | 2017-04-19 | 北京世界星辉科技有限公司 | Server connection method and server system |
| CN106202176A (en) * | 2016-06-27 | 2016-12-07 | 武汉斗鱼网络科技有限公司 | A kind of method and system realizing website version heat upgrading |
| CN106210022A (en) * | 2016-06-29 | 2016-12-07 | 天涯社区网络科技股份有限公司 | A kind of system and method for processing forum's height concurrent data requests |
| CN106897053B (en) * | 2016-07-08 | 2020-06-26 | 阿里巴巴集团控股有限公司 | Code publishing method and device |
| CN107071066A (en) * | 2017-06-07 | 2017-08-18 | 北京潘达互娱科技有限公司 | page access method and device |
| CN107463422A (en) * | 2017-07-20 | 2017-12-12 | 阿里巴巴集团控股有限公司 | Code dispositions method and device, electronic equipment |
-
2019
- 2019-07-29 CN CN201910689537.6A patent/CN110442395B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105786531A (en) * | 2014-12-19 | 2016-07-20 | 江苏融成嘉益信息科技有限公司 | Cooperative work method for online software update and data encryption |
| CN105302895A (en) * | 2015-10-21 | 2016-02-03 | 浪潮通用软件有限公司 | Data caching synchronization method, server and client side |
| CN107133234A (en) * | 2016-02-29 | 2017-09-05 | 阿里巴巴集团控股有限公司 | The method of data cached renewal, apparatus and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110442395A (en) | 2019-11-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108536761B (en) | Report data query method and server | |
| US7168077B2 (en) | System and method of executing and controlling workflow processes | |
| US11573965B2 (en) | Data partitioning and parallelism in a distributed event processing system | |
| CN110442395B (en) | Method and device for releasing product configuration data, front-end server and back-end server | |
| US9002802B2 (en) | High throughput, reliable replication of transformed data in information systems | |
| CN107958010B (en) | Method and system for online data migration | |
| US9122804B2 (en) | Logic validation and deployment | |
| US20170351989A1 (en) | Providing supply chain information extracted from an order management system | |
| EP3279812B1 (en) | Techniques for data extraction | |
| CN107562459B (en) | Management system, interface generating/displaying/operating method, medium, and terminal | |
| CN107403110A (en) | HDFS data desensitization method and device | |
| CN113962597A (en) | Data analysis method and device, electronic equipment and storage medium | |
| EP2904520B1 (en) | Reference data segmentation from single to multiple tables | |
| CN112445860A (en) | Method and device for processing distributed transaction | |
| CN114116509A (en) | Program analysis method, program analysis device, electronic device, and storage medium | |
| CN113297028A (en) | Script execution method and device, computer equipment and storage medium | |
| CN110764745B (en) | Variable transmission and collection method, device and computer readable storage medium | |
| CA3202557C (en) | A data distribution method, apparatus, device and storage medium | |
| US9384120B2 (en) | Testing of transaction tracking software | |
| CN115658248A (en) | Task scheduling method and device, electronic equipment and storage medium | |
| CN115310127A (en) | Data desensitization method and device | |
| CN114139514A (en) | Intelligent report generation method and device and computer storage medium | |
| CN114003603A (en) | Data export method, system and storage medium based on big data platform | |
| CN110045961B (en) | Management method and management platform of business rules | |
| US9286112B2 (en) | Determining and dispatching processing agent for transaction processing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |