CN110555064A - data service system and method for insurance business - Google Patents
data service system and method for insurance business Download PDFInfo
- Publication number
- CN110555064A CN110555064A CN201810257215.XA CN201810257215A CN110555064A CN 110555064 A CN110555064 A CN 110555064A CN 201810257215 A CN201810257215 A CN 201810257215A CN 110555064 A CN110555064 A CN 110555064A
- Authority
- CN
- China
- Prior art keywords
- data
- insurance
- platform
- service
- service request
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
Abstract
The application discloses a data service system for insurance business, including: the reverse proxy server is used for receiving the insurance service request, sending the insurance service request to at least one basic platform system and receiving a processing result returned by the basic platform system; the system comprises at least one basic platform system, a reverse proxy server and a data service platform, wherein the basic platform system is used for converting the format of an insurance service request, sending the converted insurance service request to the corresponding data service platform according to the type of the insurance service request, receiving a processing result returned by the data service platform, converting the format of the processing result and returning the converted insurance service request to the reverse proxy server; the at least one data service platform is used for processing insurance service data in the memory database cluster aiming at the insurance service request after format conversion sent by the basic platform system and returning a processing result to the basic platform system; the memory database cluster stores insurance business data. The problem of poor data service reliability of the existing data service system for insurance business is solved.
Description
Technical Field
the application relates to the field of data processing, in particular to a data service system for insurance business. The application also relates to a method for providing data service for insurance business.
Background
As shown in fig. 1, a data dictionary system receives an insurance service request from a branch office caller system, processes insurance service data in a corresponding branch office data dictionary database for the insurance service request, and returns a processing result for the insurance service request to the branch office caller system; the main data management system collects insurance business data of group companies in non-real time and distributes the insurance business data for branch companies to the data dictionary database of each branch company.
Since the main data management system collects, summarizes and distributes the insurance service data to the data dictionary databases of the branch companies in a non-real-time manner, if the insurance service data used for the insurance service request is not distributed to the corresponding branch company data dictionary database when the data dictionary system processes the insurance service request sent by a certain branch company calling party system, the data service cannot be provided for the insurance service request. In addition, because the insurance business data directly used by the data dictionary system for processing the received insurance service request is distributed to the data dictionary database of each branch company by the group company, if data is wrongly issued in the distribution process, the data dictionary system can use wrong data when processing the insurance service request, thereby providing wrong data service.
Therefore, the data service system for insurance business shown in fig. 1 has a problem of poor reliability of data service.
Disclosure of Invention
the application provides a data service system for insurance business, which aims to solve the problem of poor reliability of data service in the existing data service system for insurance business.
the application also provides a method for providing data service for insurance business.
The application provides a data service system for insurance business, including: the system comprises a reverse proxy server, at least one basic platform system, at least one data service platform and a memory database cluster;
The reverse proxy server is used for receiving an insurance service request, sending the insurance service request to at least one basic platform system and receiving a processing result which is returned by the basic platform system and aims at the insurance service request;
The basic platform system is used for converting the format of the insurance service request, sending the insurance service request after the format conversion to a data service platform capable of processing the insurance service request according to the type of the insurance service request, receiving a processing result which is returned by the data service platform and aims at the insurance service request, converting the format of the processing result returned by the data service platform, and returning the processing result returned by the data service platform after the format conversion to the reverse proxy server;
The data service platform is used for processing insurance service data in the memory database cluster aiming at the insurance service request after format conversion sent by the basic platform system and returning a processing result aiming at the insurance service request after format conversion to the basic platform system;
The memory database cluster comprises at least one memory database server, stores insurance business data and processes the insurance business data by matching with the data service platform.
optionally, the reverse proxy server is specifically configured to determine a first base platform system that processes the insurance service request in a manner of polling the base platform systems or according to access weights of the base platform systems, and send the insurance service request to the first base platform system.
Optionally, the basic platform system is specifically configured to convert an insurance service request in an XML format into an insurance service request in a JSON format, and convert a processing result in the JSON format for the insurance service request into a processing result in the XML format for the insurance service request.
Optionally, the data service platform is specifically configured to register a service type that the data service platform can provide to a service bus; the basic platform system is specifically used for addressing the data service platform capable of processing the insurance service request through the service bus according to the type of the insurance service request and the service type registered to the service bus by the data service platform.
Optionally, the service bus is a lightweight service bus implemented based on SpringCloud Erueka.
optionally, the data service platform provides a data service application of insurance business through a self-contained middleware developed based on a Spring Boot technology and a Jar file capable of being self-started.
Optionally, the base platform system and the data service platform specifically operate on a cloud platform based on Docker, where the cloud platform is configured to manage distribution and elastic expansion of the base platform system and the data service platform, and monitor an operating environment of the base platform system and the data service platform.
optionally, the method further includes: insurance business data dictionary database, sales management database, data inventory platform and data synchronization system, wherein,
The insurance business data dictionary database is used for collecting basic data from the main data management system, insurance product information from the product innovation engine system and first insurance business data from the sales management system;
The sales management database is used for collecting second insurance business data from the sales management system;
The data clearing platform is used for acquiring difference data between the insurance business data dictionary database, the sales management database and the memory database cluster and pushing the difference data into a message queue;
And the data synchronization system is used for monitoring the message queue, acquiring the difference data and importing the difference data into the memory database cluster.
optionally, the system further comprises a data dictionary system, which is used for storing the basic data from the main data management system, the insurance product information from the product innovation engine system and the first insurance business data collected from the sales management system into the insurance business data dictionary database.
Optionally, the at least one data service platform processes the basic data from the main data management system, the insurance product information from the product innovation engine system, and the first insurance business data and the second insurance business data from the sales management system, respectively.
optionally, the data sorting platform is specifically configured to capture change data from a database log in real time through a data log capture technology to generate difference data in an XML format.
Optionally, the system further includes a data consistency check system, configured to perform consistency check on data in the insurance business data dictionary database and the sales management database at regular time and data in the memory database cluster, generate a check report, obtain difference data between the data in the insurance business data dictionary database and the sales management database and the data in the memory database cluster according to the check report, and import the difference data into the memory database cluster.
Optionally, the consistency check includes at least one of the following checks:
Checking the number consistency of insurance service data tables;
Checking the structural consistency of the insurance business data table;
checking the consistency of the data number of the insurance business data table;
And checking the consistency of the fields of the insurance service data table.
Optionally, the data consistency check system is configured to, when the memory database of the memory database cluster is initialized, fully import the data in the insurance business data dictionary database and the sales management database into the memory database cluster.
The present application further provides a method for providing data service for insurance business, which is suitable for an insurance business data service system, and the insurance business data service system includes: the method for providing the data service for the insurance business comprises the following steps:
The reverse proxy server receives an insurance service request and sends the insurance service request to at least one basic platform system;
The basic platform system converts the format of the insurance service request and sends the insurance service request after the format conversion to a data service platform capable of processing the insurance service request according to the type of the insurance service request;
the data service platform processes insurance service data in the memory database cluster aiming at the insurance service request after format conversion sent by the basic platform system and returns a processing result aiming at the insurance service request after format conversion to the basic platform system;
And the basic platform system receives the processing result which is returned by the data service platform and aims at the insurance service request, converts the format of the processing result returned by the data service platform, and returns the processing result returned by the data service platform after format conversion to the reverse proxy server.
Optionally, the sending the insurance service request to at least one base platform system includes:
and determining a first basic platform system for processing the insurance service request in a mode of polling basic platform systems or according to the access weight of each basic platform system, and sending the insurance service request to the first basic platform system.
Optionally, the converting the format of the insurance service request includes: converting the insurance service request in the XML format into an insurance service request in a JSON format;
correspondingly, the converting the format of the processing result returned by the data service platform includes: and converting the processing result in the JSON format aiming at the insurance service request into the processing result in the XML format aiming at the insurance service request.
optionally, the sending the insurance service request after the format conversion to a data service platform capable of processing the insurance service request according to the type of the insurance service request includes:
The basic platform system is addressed to a data service platform capable of processing the insurance service request according to the type and the service bus of the insurance service request; wherein the data service platform registers the service types which can be provided by the data service platform to the service bus.
Optionally, the insurance business data service system further includes an insurance business data dictionary database, a sales management database, a data clearing platform, and a data synchronization system, and the method further includes:
The data sorting platform acquires difference data between the insurance business data dictionary database, the sales management database and the memory database cluster, and pushes the difference data into a message queue;
the data synchronization system monitors the message queue, acquires the difference data and imports the difference data into the memory database cluster;
The insurance business data dictionary database stores basic data from a main data management system, insurance product information from a product innovation engine system and first insurance business data from a sales management system;
the sales management database stores second insurance business data from the sales management system.
optionally, the obtaining, by the data sorting platform, difference data between the insurance service data dictionary database, the sales management database, and the memory database cluster includes: the data sorting platform captures changed data in real time from a database log by adopting a data log capturing technology to generate difference data in an XML format.
Optionally, the insurance business data service system further includes a data consistency check system, and correspondingly, the method further includes: the data consistency checking system regularly performs consistency checking on data in an insurance business data dictionary database and a sales management database and data in the memory database cluster to generate a checking report, acquires difference data between the data in the insurance business data dictionary database and the sales management database and the data in the memory database cluster according to the checking report, and imports the difference data into the memory database cluster.
Optionally, the consistency check includes at least one of the following checks: the method comprises the steps of insurance business data table number consistency check, insurance business data table structure consistency check, insurance business data table data number consistency check and insurance business data table field consistency check.
Optionally, the method further includes: and when the memory database of the memory database cluster is initialized, the data consistency checking system conducts full data import on the data in the insurance business data dictionary database and the sales management database to the memory database cluster.
compared with the prior art, the method has the following advantages:
According to the data service system for the insurance business, the insurance business data required by processing the insurance service request are directly provided by adopting the memory database cluster, and the process that the group company collects the insurance business data in a non-real-time manner and then distributes the insurance business data to each branch company is not needed, so that the problem that the existing data service system for the insurance business is poor in data service reliability is solved. In addition, the data are directly stored in the memory by adopting the memory database cluster, and compared with the method for accessing the data from a disk, the data quick access capability is improved. Meanwhile, the insurance service request is received by the reverse proxy server, and can be distributed according to the processing capacity of each basic platform system and each data service platform, so that the concurrent processing capacity of the insurance service request is improved.
drawings
FIG. 1 is a schematic diagram of a prior art data service system for insurance services;
FIG. 2 is a schematic diagram of a data service system for insurance services according to an embodiment of the present disclosure;
Fig. 3 is a system structure diagram of a data cloud service platform provided in an embodiment of the present application;
fig. 4 is a process flow diagram of a method for providing data services for insurance services according to an embodiment of the present application.
Detailed Description
in the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
The application provides a data service system for insurance business. The application also provides a method for providing data service for insurance business. Details are described in the following examples one by one.
a data service system for insurance business provided by the embodiment of the present application is described below with reference to fig. 2 and 3. Fig. 2 is a schematic diagram of a data service system for insurance business provided by an embodiment of the present application; fig. 3 is a system structure diagram of a data cloud service platform for actual deployment of a data service system for insurance business provided in an embodiment of the present application.
The data service system for insurance business shown in fig. 2 includes: the system comprises a reverse proxy server 201, at least one basic platform system 202, at least one data service platform 203 and a memory database cluster 204.
The reverse proxy server 201 is configured to receive an insurance service request, send the insurance service request to at least one base platform system, and receive a processing result for the insurance service request returned by the base platform system.
in the embodiment of the application, the reverse proxy server is used for realizing service load balancing, namely distributing the received insurance service request according to a certain strategy. Specifically, the reverse proxy server determines a first base platform system for processing the insurance service request by polling the base platform systems or according to the access weights of the base platform systems, and sends the insurance service request to the first base platform system. The polling means that the received insurance service requests are sequentially sent to a basic platform system capable of receiving the insurance service requests according to the sequence. And the access weight of each basic platform system is a polling weight configured according to the processing capacity of each basic platform system for the insurance service request, and the insurance service request in the corresponding proportion is sent to the basic platform system capable of processing the insurance service request according to the polling weight. For example, using Nginx as a reverse proxy server, configuring a proxy address when accessing each basic platform system on Nginx (configured by proxy _ pass parameter on Nginx), so that all insurance service requests accessing the basic platform system will first pass through the Nginx reverse proxy server, and setting an access weight of each basic platform system in an updream configuration part (configured with upstream server related parameter) in a Nginx configuration file.
taking an example of requesting the data service system for insurance service to acquire product information, the specific processing performed by the reverse proxy server 201 is described as follows: for example, the data service system for insurance business includes a first basic platform system, a second basic platform system, and a third basic platform system, and all of the data service systems can process an insurance service request requesting to acquire product information, where the three basic platform systems are respectively connected to Nginx, and access weights set by the Nginx for the three basic platform systems are respectively 3, 2, and 1, and then the probability that the Nginx sends an insurance service request acquiring product information to the first basic platform system is 3 times that sent to the third basic platform system, for example, the ngx selects to send the insurance service request to the first basic platform system with the access weight of 3 for processing, and the corresponding Nginx receives a processing result for the insurance service request returned by the first basic platform system.
The basic platform system 202 is configured to convert the format of the insurance service request, send the insurance service request after format conversion to a data service platform capable of processing the insurance service request according to the type of the insurance service request, receive a processing result for the insurance service request returned by the data service platform, convert the format of the processing result returned by the data service platform, and return the processing result returned by the data service platform after format conversion to the reverse proxy server.
Preferably, the basic platform system is specifically configured to convert an insurance service request in an XML (Extensible Markup Language) format into an insurance service request in a JSON (JavaScript Object Notation) format, and convert a processing result in the JSON format for the insurance service request into a processing result in the XML format for the insurance service request. XML is a markup language used for marking electronic files to have a structure, and is commonly used for representing data in a structured mode by using texts; JSON is a text format for representing data.
Preferably, the data service system for insurance business further comprises a service bus, and the data service platform registers the service types which can be provided by the data service platform to the service bus; the basic platform system is specifically used for addressing the data service platform capable of processing the insurance service request through the service bus according to the type of the insurance service request and the service type registered to the service bus by the data service platform. In the embodiment of the present application, the service bus is a lightweight service bus implemented based on a SpringCloud Erueka. Wherein the SpringCloud Erueka is part of a micro service suite for providing service registration and discovery functions.
Specifically, in this embodiment of the present application, the base platform system receives the insurance service request forwarded by the reverse proxy server 201, and obtains a request type from the insurance service request. Among them, the basic platform System, also called BasePlatform System, is abbreviated as BPS. For example, following the example of requesting the data service system for insurance business to acquire product information, the first base platform system receives an insurance service request for acquiring a product information table, and performs the following processing:
The message format of the insurance service request is an XML format, the type of the service request analyzed by the first basic platform system is a getRisk (request type name for acquiring product information in the example) request, and the insurance service request is converted into a JSON format from the XML format;
The first base platform system judges whether the getRisk request is addressed to the spring cloud Erueka service bus once or not, and if not, addressing is initiated to the spring cloud Erueka service bus according to the getRisk request; the SpringCloud Erueka service bus returns the address of the first data service platform that can handle the getRef request;
The first base platform system sends a getRisk request in a JSON format to the first data service platform;
The first base platform system receives a JSON format processing result returned by the first data service platform for the getRisk request, converts the JSON format processing result into an XML format message, and returns the XML format message to the reverse proxy server 201.
the data service platform 203 is configured to process insurance service data in the memory database cluster for the insurance service request after format conversion sent by the basic platform system, and return a processing result for the insurance service request after format conversion to the basic platform system.
Preferably, the data service platform is a self-contained middleware based on Spring Boot technology, and a data service application for providing insurance services by using a Jar (Java Archive) file capable of self-starting. The Spring Boot is a technical means for enabling developers to rapidly develop applications by simplifying configuration aiming at application development based on a Spring framework. Specifically, in the embodiment of the present application, the Jar file is a data processing logic and a data service that provide insurance services, and is manufactured as an executable file that is booted and booted.
The Data service system for insurance business provided by the embodiment of the application plans the number of Data service platforms according to the business granularity and the principle of exclusive function in actual implementation, and the Data service platforms are also called Data service platforms, which are abbreviated as DSP.
The insurance business data processed by the data service system for insurance business has three sources, including: a master data management system 205, a product innovation engine system 206, and a sales management system 207, wherein the master data management system 205 is used for configuring basic data; the product innovation engine system 206 is used to configure insurance product information; the sales management system 207 is used to configure first insurance business data and second insurance business data, such as sales agent and agent contract information. The at least one data service platform respectively processes basic data from the main data management system, insurance product information from the product innovation engine system and first insurance business data and second insurance business data from the sales management system. Preferably, the data service system for insurance business provides 3 data service platforms to respectively perform business logic processing on the basic data from the main data management system, the insurance product information from the product innovation engine system and the first insurance business data and the second insurance business data from the sales management system, and provide insurance business data service.
Continuing to use the example of requesting the data service system for insurance business to acquire product information, the first data service platform receives a getreply request in a JSON format for acquiring a product information table from the first base platform system, requests the memory database cluster 204 to query the product information table, acquires a query result returned by the memory database cluster 204, and assembles the query result into a return message in the JSON format and returns the return message to the first base platform system.
Preferably, the base platform system 202 and the data service platform 203 specifically operate on a cloud platform based on Docker, where the cloud platform is configured to manage distribution and elastic expansion and contraction of the base platform system and the data service platform, and monitor an operating environment of the base platform system and the data service platform.
In the embodiment of the application, the basic platform system and the data service platform provide service applications in a micro-service mode, the service applications are provided by self-contained middleware and self-starting Jar files generated based on a Spring Boot technology, and the service applications run on a private cloud CAAS based on Docker. So-called CAAS (Container Paas), is a Container Paas cloud platform based on Docker; among them, the so-called Paas (Platform As service) is a service that provides hardware, an operating system, a programming language, a development library, and a deployment tool by a cloud Platform, thereby helping a software developer to develop software more quickly. Specifically, at least one basic platform system and at least one data service platform are operated on the private cloud CAAS, the basic platform systems and the data service platforms can be expanded and contracted independently, and the data service of each basic platform system and each data service platform defines a clear boundary and is not limited by an internal independent process. In addition, the private cloud CAAS is a cloud platform developed based on a SpringCloud framework, can arrange and manage services by monitoring the calling condition of each basic platform system and each data service platform, manage the release and elastic expansion of each basic platform system and each data service platform, and monitor the operating environment of the basic platform systems and the data service platforms, and can effectively reduce the operation and maintenance workload. The management of the release comprises that when the system version is changed and the old version is returned, a certain version is automatically released and updated to the application environment; the elastic expansion means that computing resources are automatically adjusted according to business requirements and preset strategies, so that the number of cloud servers is automatically increased along with the increase of business load and reduced along with the reduction of business load, and the stable and healthy operation of business is ensured, for example: and if the average CPU occupancy rate of the Docker container exceeds the threshold value, such as 70%, 2 Dockers are added for capacity expansion.
the Docker is an open-source Container engine based on lightweight LXC (Linux Container), and in practical applications, the developed applications need to be packaged into a Docker Container and then distributed to a Linux machine for running. Specifically, in the embodiment of the application, the applications provided by the basic platform system and the data service platform are printed into Jar packages through a command line, a Docker mirror image is constructed in a Docker build (namely, a command for establishing a mirror image) mode, and the application can be accessed according to a specified port after the mirror image is operated. Because the Docker container is started just like a starting process, the starting speed is generally in the millisecond (second level) level, and the method is much faster than the traditional virtual machine mode, so that the cloud platform based on the Docker can easily cope with the burst access amount. In addition, the Docker container is kernel-level virtualization, which can achieve higher performance and efficiency, and can run on almost any platform, including a physical machine, a virtual machine, a public cloud, a private cloud, a personal computer, a server and the like, and the compatibility can enable a user to directly migrate an application program from one platform to another platform, so that the migration and the expansion are easier.
The memory database cluster 204 includes at least one memory database server, stores insurance business data, and processes the insurance business data in cooperation with the data service platform.
the memory database is a database in which data is directly stored in a memory and operated, and can provide a high-speed data access capability. The embodiment of the application provides the distributed memory database in a cluster mode, the data are distributed on different host systems for use, and uninterrupted service can be supported through free switching. The method specifically adopts a VoltDB memory database cluster, wherein VoltDB is a memory database, the VoltDB memory database cluster comprises a plurality of VoltDB memory database server nodes, a virtual single database logic image is externally provided through a main node, the processing capacity can be improved approximately linearly by adding nodes in the cluster, and data on the memory can be protected by storing a plurality of data copies.
Preferably, the data service system for insurance services further includes an insurance service data dictionary database 208 and a sales management database 209, a data sorting platform 210, and a data synchronization system 211, where the insurance service data dictionary database 209 and the sales management database 208 are source databases providing insurance service data for the memory data cluster 204, and the data sorting platform 210 and the data synchronization system 211 cooperate to complete synchronization of insurance service data from the source databases to the memory database cluster 204. Specifically, the insurance service data dictionary database 208 is used for collecting basic data from the main data management system 205, insurance product information from the product innovation engine system 206, and first insurance service data from the sales management system 207, for example, the insurance service data dictionary database is implemented by using an Informix example. The sales management database 209 is used to collect the second insurance service data from the sales management system 207, for example, by using an Informix instance. The data inventory platform 210 is configured to obtain difference data between the insurance business data dictionary database 208 and the sales management database 209, and the memory database cluster 204, and push the difference data into a message queue; the data synchronization system is configured to monitor the message queue, obtain the difference data, and import the difference data into the memory database cluster 204.
Preferably, the data service system for insurance business further includes a data dictionary system 213 for storing the basic data from the main data management system 205, the insurance product information from the product innovation engine system 206, and the first insurance business data from the sales management system 207 to the insurance business data dictionary database 208.
Specifically, in the embodiment of the present application, the Data sorting platform captures change Data in real time from a database log to generate difference Data in an XML format for the insurance service Data dictionary database 208 and the sales management database 209 through a Data log Capture technology (Changed Data Capture, CDC), and pushes the difference Data into a Message Queue (MQ) to achieve fast Data synchronization. For example, the changed data is discovered through a data log capturing technology, and an XML data message is generated for each row of data (namely, data change caused by adding, deleting and modifying operations of a database table) of the changed data and is pushed into the message queue; the database synchronization system monitors the message queue, analyzes difference data from XML data messages acquired from the message queue, and imports the difference data into a VoltDB memory database, thereby realizing real-time data synchronization, solving the problem of data consistency among different systems and improving the reliability of data transmission.
According to the embodiment of the application, the unified memory database is adopted to directly provide data used for processing insurance services for the data service platform, the data services are provided in a centralized mode, and the data in the memory database is synchronized with the insurance service data dictionary database and the sales management database in real time, so that a group company is not required to gather the data in a non-real-time mode and then distribute the data to the data dictionary database of each branch company, the problem that the data distribution failure of the group company to the branch companies in the existing main data management system for providing the insurance service data service causes that the service data depended on when the data service is provided cannot be updated in time is solved, and therefore reliable data service can be provided. In addition, in the existing main data management system for providing insurance business data service, since a group company has a plurality of branch companies, each branch company needs one set of operation and maintenance personnel to maintain a database and an application system, compared with the existing main data management system for providing insurance business data service, the data service system for insurance business provided by the embodiment of the application only needs the group company to maintain an insurance business data dictionary database, a sales management database, a memory database cluster and an application system in a unified manner, and the operation and maintenance labor cost can be saved.
In this embodiment, the data service system for insurance services further includes a data consistency check system 212, configured to perform consistency check on data in the insurance services data dictionary database 208 and the sales management database 209 at regular time and data in the memory database cluster 204, generate a check report, obtain difference data between the data in the insurance services data dictionary database 208 and the sales management database 209 and the data in the memory database cluster 204 according to the check report, and import the difference data into the memory database cluster 204. Specifically, the data consistency check system 212 connects the insurance service data dictionary DataBase 208 and the sales management DataBase 209 directly to the memory DataBase cluster 204 through JDBC (Java DataBase Connectivity), and performs data consistency check based on JDBC technology, where the consistency check includes at least one of the following checks: the method comprises the steps of insurance business data table number consistency check, insurance business data table structure consistency check, insurance business data table data number consistency check and insurance business data table field consistency check. For consistency check of insurance business data table structure and field, when the insurance business data dictionary database 208 and the sales database 209 are changed, the structure of the memory database cluster 204 can be changed synchronously, and the source database and the memory database directly providing service are kept consistent. For example, consistency check is performed between the insurance service data dictionary database 208 and the sales management database 209 and the memory database cluster 204 at 2 points in the morning every day, and the check time point can be configured; the data consistency check system creates a read-only user for the insurance business data dictionary database 208 and the sales management database 209, and extracts difference data according to the check report and imports the difference data into the memory database cluster 204.
It should be noted that the data consistency check system 212 may perform data consistency check at regular time, and synchronize the checked difference data from the insurance business data dictionary database 208 and the sales management database 209 to the memory database cluster 204 directly providing the data used by the data service in real time or according to a set time, and in addition, the data consistency check system 212 may efficiently import data through JDBC direct connection database, and is suitable for full import, so that when the memory database of the memory database cluster 204 is initialized, the data in the insurance business data dictionary database 208 and the sales management database 209 are fully imported into the memory database cluster 204, for example, when the memory database of the memory database cluster 204 is initialized, the insurance business data does not exist in the memory database of the memory database cluster 204, and the data consistency check system performs data consistency check on the insurance business data dictionary database and the sales management database The total amount of the data is imported into a VoltDB memory database of the memory database cluster as initial data.
For example, a nationwide DCSP (Data Cloud Service Platform) deployed by a group company is a specific example of the Data Service system for insurance services actually deployed, and fig. 3 shows a system structure of the DCSP, where the Data sources of the DCSP providing the Data Service for insurance services include three: from the master data management system 301, the product innovation engine system 302, and the sales management system 303, data collected from these systems is similar to a write operation, and the collected data is stored in the data dictionary database 305 and the sales management database 306; wherein, the master data management system 301 is used for configuring basic data; the product innovation engine system 302 is used to configure insurance product information; the sales management system 303 is configured to configure first insurance business data and second insurance business data; the data dictionary system 304 stores data from the main data management system 301, data from the product innovation engine system 302 and first insurance business data from the sales management system 303 into the data dictionary database 305; the second insurance business data from the sales management system 303 is specifically stored in the sales management database 306; the data dictionary database 305 and the sales management database 306 serve as source databases to synchronize the stored data thereof to a distributed memory database cluster 310 in real time through a data sorting platform 307 and a data synchronization 308, the distributed memory database cluster 310 directly provides insurance business data on which the DCSP provides data services to the outside, and the distributed memory database cluster 310 comprises a plurality of memory database server nodes, such as a memory database 310-1, a memory database 310-2 and a memory database 310-3. The DCSP receives an insurance service request of a caller system through nginnx (311) and returns a processing result for the insurance service request, and this method of accessing the service is similar to a read operation of data. The DCSP includes 3 base platform systems: BPS (312-1), BPS (312-2), BPS (312-3), these 3 basic platform systems correspond to the data service platform respectively: the DSPA product direction is 313-1, the DSPB code direction is 313-2, and the DSPC marketing direction is 313-3; the method comprises the following steps that Nginx (311) sends a received insurance service request to at least one basic platform system such as BPS (312-1), the BPS (312-1) converts the format of the insurance service request, specifically, converts an XML format into a JSON format, the BPS (312-1) sends the insurance service request in the JSON format obtained after the format conversion to a data service platform DSPA product capable of processing the insurance service request according to the type of the insurance service request, the DSPA product processes insurance service data in a memory database cluster 310 aiming at the insurance service request in the JSON format from 313-1 to 313-1, and the DSPA product processes the insurance service data in the memory database cluster 310 aiming at the insurance service request in the JSON format from 313-1 and returns the processing result to the BPS (312-1); wherein BPS (312-1) is the address addressed to DSPA product direction 313-1 through lightweight service bus 314; and the DSPA product acquires data required by business logic processing of the JSON format insurance service request from 313-1 from the distributed memory database cluster 310. The DCSP synchronizes the source data to the memory database directly providing the data used by the data service of the insurance business in real time through the data sorting platform 307 and the data synchronization 308, and the problem of non-real-time summarization does not exist. In addition, the DCSP also comprises a data consistency check 309 for regularly checking the data consistency of the source data and the data in the memory database cluster which directly provides the data used by the insurance business data service, thereby improving the reliability of data transmission. In addition, the basic platform system and the data service platform of the DCSP run on a Docker-based cloud platform, the core business system is split into a plurality of business modules according to specific business logic, the release of the application and the increase and decrease of the application are managed through the cloud platform, and the modification of the application is distributed and updated in an incremental mode, so that a large amount of previous updating work is replaced, the rapid online of the demand is realized, and the software development efficiency and the demand delivery speed are improved.
the DCSP example is followed. The deployment of the DCSP comprises two phases of a window period and a production operation; in the window period, the initialization of the memory database cluster 310 is completed by performing full-volume import through data consistency check 309, and insurance business data is totally imported into the memory database from the data dictionary database 305 and the sales management database 306; in the production operation stage, the real-time data synchronization from the insurance business data dictionary database and the sales management database to the memory database of the memory database cluster is completed through a data sorting platform 307 and a data synchronization 308. After the DCSP is completely deployed and replaces the existing main data management system, the hardware resource cost can be saved, for example, a data dictionary system of the existing main data management system is built by using a mini-type computer by adopting an Informix instance, a VoltDB memory database used by the DCSP uses an X86 server, and the price of the X86 server with the same computing power is only 1/20 of the mini-type computer.
on the basis of the embodiment of the data service system for the insurance business provided by the application, the application also provides a method for providing the data service for the insurance business.
Referring to fig. 4, there is shown a process flow diagram of a method for providing data services for insurance services provided in accordance with the present application. Since the method embodiment is based on the embodiment of the data service system for insurance business, the description is simple, and the relevant portions only need to refer to the corresponding description of the system embodiment.
The application provides a method for providing data service for insurance business, which is suitable for an insurance business data service system, wherein the insurance business data service system comprises: the system comprises a reverse proxy server, at least one basic platform system, at least one data service platform and a memory database cluster. The method specifically comprises the following steps: step S401 to step S404.
Step S401, the reverse proxy server receives an insurance service request and sends the insurance service request to at least one basic platform system.
The purpose of this step is to send the received insurance service request to the base platform system.
in this embodiment of the present application, the insurance service data service system includes one or more of the basic platform systems, and the reverse proxy server selects which basic platform system the insurance service request is sent to after receiving the insurance service request, specifically, determines a first basic platform system that processes the insurance service request in a manner of polling the basic platform systems or according to an access weight of each basic platform system, and sends the insurance service request to the first basic platform system. The mode of polling the basic platform system is to send the received insurance service requests to the basic platform system capable of receiving the insurance service requests in sequence. And the access weight of each basic platform system is a polling weight configured according to the processing capacity of each basic platform system for the insurance service request, and the insurance service request in the corresponding proportion is sent to the basic platform system capable of processing the insurance service request according to the polling weight.
step S402, the basic platform system converts the format of the insurance service request, and sends the insurance service request after the format conversion to a data service platform capable of processing the insurance service request according to the type of the insurance service request.
The purpose of this step is to convert the format of the insurance service request into a format that can be processed by the data service platform and then send the converted format to the data service platform that can process the insurance service request for business logic processing.
In the embodiment of the application, the reverse proxy server receives an insurance service request in an XML format, and sends the insurance service request in the XML format to the base platform system selected by the reverse proxy server, for example, if the base platform system selected by the reverse proxy server is a first base platform system, the first base platform system converts the insurance service request in the XML format into an insurance service request in a JSON format, and obtains a service type corresponding to the insurance service request, and the base platform system addresses a data service platform capable of processing the insurance service request according to the type of the insurance service request and a service bus; the data service platform registers the service types which can be provided by the data service platform to the service bus, so that the basic platform system can be addressed to the data service platform which can process the insurance service request through the service bus according to the service types of the insurance service request. In particular, the service bus is a lightweight service bus implemented based on SpringCloud Erueka.
In the embodiment of the application, the basic platform system judges whether the insurance service request is addressed to the SpringCloud Erueka service bus before being addressed according to the service type of the insurance service request, and if not, the basic platform system initiates addressing to the SpringCloud Erueka service bus according to the type of the insurance service request; the SpringCloudErueka service bus returns the address of the data service platform that can handle this type of insurance service request; and after the addressing is successful, the basic platform system sends the insurance service request in the JSON format to the data service platform.
step S403, the data service platform processes insurance service data in the memory database cluster according to the insurance service request after format conversion sent by the basic platform system, and returns the processing result of the insurance service request after format conversion to the basic platform system; the memory database cluster comprises at least one memory database server, stores insurance business data and processes the insurance business data by matching with the data service platform.
The purpose of this step is to perform business logic processing on the insurance service request after the format conversion, which is sent by the basic platform system, through the data service platform, and return a processing result to the basic platform system.
In this embodiment of the application, the data service platform receives an insurance service request in a JSON format, performs service logic processing on the insurance service request in the JSON format, stores insurance service data, which is directly relied on when performing the service logic processing, in the memory database cluster, specifically, a VoltDB memory database cluster, assembles a result obtained by the service logic processing into a processing result in the JSON format, and returns the processing result in the JSON format to the corresponding base platform system.
preferably, in this embodiment of the present application, the insurance business data service system further includes an insurance business data dictionary database, a sales management database, a data clearing platform, and a data synchronization system, where data in the insurance business data dictionary database and the sales management database are used as sources of data in the memory database cluster and synchronized in real time to the database of the memory database cluster, and specifically, the method for providing data service for insurance business further includes:
the data sorting platform acquires difference data between the insurance business data dictionary database, the sales management database and the memory database cluster, and pushes the difference data into a message queue;
The data synchronization system monitors the message queue, acquires the difference data and imports the difference data into the memory database cluster;
The insurance business data dictionary database stores basic data from a main data management system, insurance product information from a product innovation engine system and first insurance business data from a sales management system;
the sales management database stores second insurance business data from the sales management system.
specifically, the insurance business data dictionary database, the sales management database, and the memory database cluster are synchronized with each other in real time, and the difference data is obtained by the following processing: the data sorting platform captures changed data in real time from a database log by adopting a data log capturing technology to generate difference data in an XML format.
Preferably, in this embodiment of the present application, the insurance business data service system further includes a data consistency check system, and correspondingly, the method further includes: the data consistency checking system regularly performs consistency checking on data in an insurance business data dictionary database and a sales management database and data in the memory database cluster to generate a checking report, acquires difference data between the data in the insurance business data dictionary database and the sales management database and the data in the memory database cluster according to the checking report, and imports the difference data into the memory database cluster. Wherein the consistency check comprises at least one of the following checks: the method comprises the steps of insurance business data table number consistency check, insurance business data table structure consistency check, insurance business data table data number consistency check and insurance business data table field consistency check. Specifically, the difference data obtained by performing data consistency check at regular time is synchronized to the memory database cluster directly providing the used data for the data service from the insurance business data dictionary database and the sales management database in real time or according to set time.
In addition, in the embodiment of the present application, the data consistency check system directly connects the insurance service dictionary database and the sales management database to the memory database of the memory database cluster through JDBC, so that data can be efficiently imported and the data consistency check system is suitable for full-volume import.
According to the embodiment of the application, the unified memory database is adopted to directly provide data used for processing insurance services for the data service platform, the data services are provided in a centralized mode, and the data in the memory database is synchronized with the insurance service data dictionary database and the sales management database in real time, so that a group company is not required to gather the data in a non-real-time mode and then distribute the data to the data dictionary database of each branch company, the problem that the data distribution failure of the group company to the branch companies causes the problem that the service data depended when the data services are provided cannot be updated in time is solved, and reliable data services can be provided.
Step S404, the basic platform system receives the processing result for the insurance service request returned by the data service platform, converts the format of the processing result returned by the data service platform, and returns the processing result returned by the data service platform after format conversion to the reverse proxy server.
The purpose of this step is to return the processing result for the insurance service request to the reverse proxy server, and return the processing result to the caller of the insurance service request through the reverse proxy server.
In this embodiment of the present application, the processing result received by the base platform system for the insurance service request is a processing result in JSON format. And converting the format of the processing result returned by the data service platform through the basic platform system, converting the processing result in the JSON format aiming at the insurance service request into the processing result in the XML format aiming at the insurance service request, and returning the processing result in the XML format to the reverse proxy server by the basic platform system after the conversion is completed.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
the memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
1. computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
2. As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Although the present application has been described with reference to the preferred embodiments, it is not intended to limit the present application, and those skilled in the art can make variations and modifications without departing from the spirit and scope of the present application, therefore, the scope of the present application should be determined by the claims that follow.
Claims (23)
1. a data service system for insurance services, comprising: the system comprises a reverse proxy server, at least one basic platform system, at least one data service platform and a memory database cluster;
The reverse proxy server is used for receiving an insurance service request, sending the insurance service request to at least one basic platform system and receiving a processing result which is returned by the basic platform system and aims at the insurance service request;
The basic platform system is used for converting the format of the insurance service request, sending the insurance service request after the format conversion to a data service platform capable of processing the insurance service request according to the type of the insurance service request, receiving a processing result which is returned by the data service platform and aims at the insurance service request, converting the format of the processing result returned by the data service platform, and returning the processing result returned by the data service platform after the format conversion to the reverse proxy server;
The data service platform is used for processing insurance service data in the memory database cluster aiming at the insurance service request after format conversion sent by the basic platform system and returning a processing result aiming at the insurance service request after format conversion to the basic platform system;
The memory database cluster comprises at least one memory database server, stores insurance business data and processes the insurance business data by matching with the data service platform.
2. The system of claim 1, wherein the reverse proxy server is specifically configured to determine a first base platform system for processing the insurance service request by polling the base platform systems or according to access weights of the base platform systems, and send the insurance service request to the first base platform system.
3. The system according to claim 1, wherein the base platform system is specifically configured to convert the insurance service request in the XML format into the insurance service request in the JSON format, and convert the processing result in the JSON format for the insurance service request into the processing result in the XML format for the insurance service request.
4. The system according to claim 1, characterized in that the data service platform is specifically configured to register the types of services that it can provide to the service bus; the basic platform system is specifically used for addressing the data service platform capable of processing the insurance service request through the service bus according to the type of the insurance service request and the service type registered to the service bus by the data service platform.
5. the system of claim 4, wherein the service bus is a lightweight service bus implemented based on SpringCloud Erueka.
6. The system according to claim 1, wherein the data service platform provides a data service application of insurance services, in particular through self-contained middleware developed based on Spring Boot technology, a Jar file capable of self-starting.
7. The system according to claim 1, wherein the base platform system and the data service platform specifically run on a cloud platform based on Docker, wherein the cloud platform is configured to manage distribution and elastic expansion and contraction of the base platform system and the data service platform, and monitor an operating environment of the base platform system and the data service platform.
8. The system of claim 1, further comprising: insurance business data dictionary database, sales management database, data inventory platform and data synchronization system, wherein,
The insurance business data dictionary database is used for collecting basic data from the main data management system, insurance product information from the product innovation engine system and first insurance business data from the sales management system;
the sales management database is used for collecting second insurance business data from the sales management system;
The data clearing platform is used for acquiring difference data between the insurance business data dictionary database, the sales management database and the memory database cluster and pushing the difference data into a message queue;
And the data synchronization system is used for monitoring the message queue, acquiring the difference data and importing the difference data into the memory database cluster.
9. the system of claim 8, further comprising a data dictionary system for storing base data from a data management system, insurance product information from a product innovation engine system, and first insurance business data collected from a sales management system to the insurance business data dictionary database.
10. The system of claim 9, wherein the at least one data service platform processes base data from the master data management system, insurance product information from the product innovation engine system, and first and second insurance business data from the sales management system, respectively.
11. The system of claim 8, wherein the data inventory platform is specifically configured to capture change data from database logs in real-time to generate XML-formatted difference data through a data log capture technique.
12. the system according to claim 1, further comprising a data consistency check system for performing consistency check with the data in the memory database cluster for the data in the insurance business data dictionary database and the sales management database at regular time, generating a check report, acquiring difference data between the data in the insurance business data dictionary database and the sales management database and the data in the memory database cluster according to the check report, and importing the difference data into the memory database cluster.
13. the system of claim 12, wherein the consistency check comprises at least one of:
Checking the number consistency of insurance service data tables;
Checking the structural consistency of the insurance business data table;
Checking the consistency of the data number of the insurance business data table;
And checking the consistency of the fields of the insurance service data table.
14. the system of claim 12, wherein the data consistency check system is configured to import the data in the insurance services data dictionary database and the sales management database to the memory database cluster at a full capacity upon initialization of the memory database cluster.
15. A method for providing data service for insurance business, which is applicable to an insurance business data service system, and the insurance business data service system comprises: reverse proxy server, at least one basic platform system, at least one data service platform, memory database cluster, its characterized in that includes:
The reverse proxy server receives an insurance service request and sends the insurance service request to at least one basic platform system;
The basic platform system converts the format of the insurance service request and sends the insurance service request after the format conversion to a data service platform capable of processing the insurance service request according to the type of the insurance service request;
the data service platform processes insurance service data in the memory database cluster aiming at the insurance service request after format conversion sent by the basic platform system and returns a processing result aiming at the insurance service request after format conversion to the basic platform system;
and the basic platform system receives the processing result which is returned by the data service platform and aims at the insurance service request, converts the format of the processing result returned by the data service platform, and returns the processing result returned by the data service platform after format conversion to the reverse proxy server.
16. The method of claim 15, wherein said issuing said insurance service request to at least one base platform system comprises:
And determining a first basic platform system for processing the insurance service request in a mode of polling basic platform systems or according to the access weight of each basic platform system, and sending the insurance service request to the first basic platform system.
17. The method of claim 15, wherein converting the format of the insurance service request comprises: converting the insurance service request in the XML format into an insurance service request in a JSON format;
Correspondingly, the converting the format of the processing result returned by the data service platform includes: and converting the processing result in the JSON format aiming at the insurance service request into the processing result in the XML format aiming at the insurance service request.
18. The method according to claim 15, wherein the sending the insurance service request after format conversion to a data service platform capable of processing the insurance service request according to the type of the insurance service request comprises:
the basic platform system is addressed to a data service platform capable of processing the insurance service request according to the type and the service bus of the insurance service request; wherein the data service platform registers the service types which can be provided by the data service platform to the service bus.
19. the method according to claim 15, wherein the insurance business data service system further comprises an insurance business data dictionary database, a sales management database, a data inventory platform, and a data synchronization system, the method further comprising:
The data sorting platform acquires difference data between the insurance business data dictionary database, the sales management database and the memory database cluster, and pushes the difference data into a message queue;
The data synchronization system monitors the message queue, acquires the difference data and imports the difference data into the memory database cluster;
The insurance business data dictionary database stores basic data from a main data management system, insurance product information from a product innovation engine system and first insurance business data from a sales management system;
The sales management database stores second insurance business data from the sales management system.
20. The method of claim 19, wherein said data inventory platform obtaining difference data between said insurance services data dictionary database and said sales management database, and said memory database cluster, comprises: the data sorting platform captures changed data in real time from a database log by adopting a data log capturing technology to generate difference data in an XML format.
21. The method according to claim 15, wherein the insurance business data service system further comprises a data consistency check system, and wherein the method further comprises: the data consistency checking system regularly performs consistency checking on data in an insurance business data dictionary database and a sales management database and data in the memory database cluster to generate a checking report, acquires difference data between the data in the insurance business data dictionary database and the sales management database and the data in the memory database cluster according to the checking report, and imports the difference data into the memory database cluster.
22. the method of claim 21, wherein the consistency check comprises at least one of: the method comprises the steps of insurance business data table number consistency check, insurance business data table structure consistency check, insurance business data table data number consistency check and insurance business data table field consistency check.
23. the method of claim 21, further comprising: and when the memory database of the memory database cluster is initialized, the data consistency checking system conducts full data import on the data in the insurance business data dictionary database and the sales management database to the memory database cluster.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810257215.XA CN110555064A (en) | 2018-03-27 | 2018-03-27 | data service system and method for insurance business |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810257215.XA CN110555064A (en) | 2018-03-27 | 2018-03-27 | data service system and method for insurance business |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110555064A true CN110555064A (en) | 2019-12-10 |
Family
ID=68733784
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810257215.XA Pending CN110555064A (en) | 2018-03-27 | 2018-03-27 | data service system and method for insurance business |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110555064A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111475490A (en) * | 2020-04-28 | 2020-07-31 | 国网河南省电力公司信息通信公司 | Data management system and method for data directory system |
| CN111861763A (en) * | 2020-07-28 | 2020-10-30 | 贵州力创科技发展有限公司 | Vehicle insurance anti-fraud system and method based on big data management |
| CN112288585A (en) * | 2020-11-20 | 2021-01-29 | 中国人寿保险股份有限公司 | Insurance business actuarial data processing method and device and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101997854A (en) * | 2009-08-31 | 2011-03-30 | 阿里巴巴集团控股有限公司 | Processing system and method for providing data service |
| CN102780768A (en) * | 2012-06-29 | 2012-11-14 | 北京奇虎科技有限公司 | Processing method and processing system for highly-concurrent requests |
| US20130191509A1 (en) * | 2012-01-19 | 2013-07-25 | Microsoft Corporation | Techniques to provide proxies for web services |
| CN104333573A (en) * | 2012-06-29 | 2015-02-04 | 北京奇虎科技有限公司 | Processing method and processing system for highly-concurrent requests |
| CN107305576A (en) * | 2016-04-25 | 2017-10-31 | 北京京东尚科信息技术有限公司 | The pseudo- static treatment method and apparatus of the page |
-
2018
- 2018-03-27 CN CN201810257215.XA patent/CN110555064A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101997854A (en) * | 2009-08-31 | 2011-03-30 | 阿里巴巴集团控股有限公司 | Processing system and method for providing data service |
| US20130191509A1 (en) * | 2012-01-19 | 2013-07-25 | Microsoft Corporation | Techniques to provide proxies for web services |
| CN102780768A (en) * | 2012-06-29 | 2012-11-14 | 北京奇虎科技有限公司 | Processing method and processing system for highly-concurrent requests |
| CN104333573A (en) * | 2012-06-29 | 2015-02-04 | 北京奇虎科技有限公司 | Processing method and processing system for highly-concurrent requests |
| CN107305576A (en) * | 2016-04-25 | 2017-10-31 | 北京京东尚科信息技术有限公司 | The pseudo- static treatment method and apparatus of the page |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111475490A (en) * | 2020-04-28 | 2020-07-31 | 国网河南省电力公司信息通信公司 | Data management system and method for data directory system |
| CN111475490B (en) * | 2020-04-28 | 2023-04-25 | 国网河南省电力公司信息通信公司 | Data management system and method of data directory system |
| CN111861763A (en) * | 2020-07-28 | 2020-10-30 | 贵州力创科技发展有限公司 | Vehicle insurance anti-fraud system and method based on big data management |
| CN111861763B (en) * | 2020-07-28 | 2024-03-22 | 贵州力创科技发展有限公司 | Vehicle insurance anti-fraud system and method based on big data management |
| CN112288585A (en) * | 2020-11-20 | 2021-01-29 | 中国人寿保险股份有限公司 | Insurance business actuarial data processing method and device and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020253347A1 (en) | Container cluster management method, device and system | |
| US10338958B1 (en) | Stream adapter for batch-oriented processing frameworks | |
| TWI549080B (en) | The method, system and device for sending information of category information | |
| CN111078504A (en) | Distributed call chain tracking method and device, computer equipment and storage medium | |
| CN103473696A (en) | Method and system for collecting, analyzing and distributing internet business information | |
| WO2019057055A1 (en) | Task processing method and apparatus, electronic device, and storage medium | |
| US9983823B1 (en) | Pre-forking replicas for efficient scaling of a distribued data storage system | |
| CN113220795B (en) | Data processing method, device, equipment and medium based on distributed storage | |
| CN110555064A (en) | data service system and method for insurance business | |
| US11321350B2 (en) | Managing identifiers for multinodal master systems of unknown or changing size | |
| CN110581893B (en) | Data transmission method and device, routing equipment, server and storage medium | |
| CN111338893A (en) | Process log processing method and device, computer equipment and storage medium | |
| CN111124589A (en) | Service discovery system, method, device and equipment | |
| CN110457059A (en) | A kind of sequence number generation method and device based on redis | |
| US20230370285A1 (en) | Block-chain-based data processing method, computer device, computer-readable storage medium | |
| CN112685499A (en) | Method, device and equipment for synchronizing process data of work service flow | |
| CN111338834B (en) | Data storage method and device | |
| CN116701330A (en) | Logistics information sharing method, device, equipment and storage medium | |
| FR3102259A1 (en) | MONITORING A DISTRIBUTED APPLICATION SERVER ENVIRONMENT | |
| CN113900810A (en) | Distributed graph processing method, system and storage medium | |
| Gupta et al. | HADOOP-An Open Source Framework for Big Data | |
| CN113656502A (en) | Data synchronization method, system, electronic device and storage medium | |
| CN112732756A (en) | Data query method, device, equipment and storage medium | |
| EP3306471B1 (en) | Automatic server cluster discovery | |
| CN113535227B (en) | Deployment method and device of digital technology architecture |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191210 |
|
| RJ01 | Rejection of invention patent application after publication |