CN107016548B - Client system, information processing method, reading and writing method and device - Google Patents
Client system, information processing method, reading and writing method and device Download PDFInfo
- Publication number
- CN107016548B CN107016548B CN201611131054.7A CN201611131054A CN107016548B CN 107016548 B CN107016548 B CN 107016548B CN 201611131054 A CN201611131054 A CN 201611131054A CN 107016548 B CN107016548 B CN 107016548B
- Authority
- CN
- China
- Prior art keywords
- client
- record
- node
- target
- client information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 69
- 230000010365 information processing Effects 0.000 title claims abstract description 24
- 238000003672 processing method Methods 0.000 title claims abstract description 21
- 230000000694 effects Effects 0.000 claims abstract description 95
- 238000010586 diagram Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 10
- 230000003993 interaction Effects 0.000 description 6
- 230000004048 modification Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
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
- G06Q30/00—Commerce
- G06Q30/01—Customer relationship services
- G06Q30/015—Providing customer assistance, e.g. assisting a customer within a business location or via helpdesk
- G06Q30/016—After-sales
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Marketing (AREA)
- Finance (AREA)
- Computational Linguistics (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Accounting & Taxation (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a client system, an information processing method, a reading and writing method and a device, which are characterized in that after a target operation request which is sent by a service system and used for operating client information is received, whether the operation flow identification is unique or not is inquired in each operation record of an activity table according to the operation flow identification carried by the target operation request, when the operation flow identification is unique, a corresponding index field used for indexing a basic table is updated in a tool table according to the target operation request, and the target operation request is recorded in the activity table. Because the activity table is adopted to record all operations of the service system aiming at the client information, and each operation has a unique operation flow identifier, repeated operation and client data confusion are avoided, the problem of data consistency under the condition of multiple concurrencies is solved, and meanwhile, the performance and the capacity of the system are improved.
Description
Technical Field
The present invention relates to information processing technologies, and in particular, to a client system, an information processing method, a read-write method, and an apparatus.
Background
In an e-commerce platform or a social platform, since the frequency of modifying client data such as a contact address, a user name, a friend list and the like is low compared with transaction records and chat records, a client system often designs and processes the client data as state type data.
Although the storage space occupied by the state data is small, and the system with modification authority can change the state data, so that the modification is flexible, in the actual maintenance process, under the condition that a plurality of parties concurrently modify the client data of the same client, the mode of taking the client information as the state data is easy to cause data recording errors. For example, as shown in fig. 1, when a system a and a system B perform a "modify mobile phone number" operation on the same customer information by using different mobile phone numbers at the same time, a prompt may appear that both the system a and the system B return a successful modification, but the mobile phone number of the customer is different for different systems, the mobile phone number of the customer is 137 for the system a, the mobile phone number of the customer is 138 for the system B, and the mobile phone number actually maintained in the customer system is one of 138 and 137. Obviously, this method is very easy to cause data confusion and data consistency problems.
If a locking mechanism is adopted, when one party modifies the client data, the client data is locked, and the other party cannot modify the same client data.
Disclosure of Invention
The invention provides a client system, an information processing method, a reading and writing method and a reading and writing device.
In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:
in a first aspect, an information processing method based on a client system is provided, the client system includes an active node for maintaining an active table, a base node for maintaining a base table, and a tool node for maintaining a tool table, the method includes:
the active node acquires a target operation request for operating the client information from a service system;
the active node inquires whether the operation flow identifier is unique in each operation record of the active table according to the operation flow identifier carried by the target operation request; wherein, the operation record is used for indicating the historical operation executed by the business system on the client information;
when the active node determines that the operation flow identifier is unique, the tool node updates the corresponding index field in the tool table according to the target operation request and returns a message of successful update to the active node; the tool table is used for indexing the customer information recorded by the basic table;
and after receiving the message of successful update, the active node records the target operation request in the active table.
In a second aspect, an information processing method based on a client system is provided, the client system comprises an active node for maintaining an active table, a base node for maintaining a base table, and a tool node for maintaining a tool table, the method comprises:
the active node acquires a target query request for querying client information from a service system;
the active node inquires the operation record of the active table whether the client in the target inquiry request is involved;
when the operation record of the client is inquired in the activity table, sending the inquired operation record of the client to the base node;
the basic node indexes according to the query field related to the target query request through a tool table in the tool node so as to query the corresponding customer information record in the basic table;
the basic node performs data combination according to the operation records of the inquired clients and the inquired client information records;
and the basic node sends a client information record obtained by data combination to the service system.
In a third aspect, a method for writing customer information is provided, the method comprising:
receiving a target operation request which is sent by a service system and used for operating client information;
inquiring whether the operation flow identification is unique in each operation record of an activity table according to the operation flow identification carried by the target operation request; wherein, the operation record is used for indicating the historical operation executed by the business system on the client information;
when the operation flow identifier is unique, updating a corresponding index field in the tool table according to the target operation request; the tool table is used for indexing the customer information recorded by the basic table;
and recording the target operation request in the activity table.
In a fourth aspect, a client information reading method is provided, the method including:
acquiring a target query request for querying client information from a service system;
querying whether the operation record of the activity table relates to the client in the target query request;
when the operation records of the clients are inquired in the active table, the inquiry fields related to the target inquiry requests are indexed through a tool table, so that the corresponding client information records are inquired in the basic table;
performing data combination according to the operation records of the inquired clients and the inquired client information records;
and sending the client information record obtained by data combination to the service system.
In a fifth aspect, a client system is provided, the client system comprising an active node, a base node, and a tool node;
the active node is used for inquiring whether the operation flow identification is unique in each operation record of the active table according to the operation flow identification carried by the target operation request after the target operation request for operating the client information is obtained from the service system; wherein, the operation record is used for indicating the historical operation executed by the business system on the client information;
the tool node is used for updating the corresponding index field in the tool table according to the target operation request when the active node determines that the operation flow identifier is unique, and returning a message of successful update to the active node; the tool table is used for indexing the customer information recorded by the basic table;
the activity table is further configured to record the target operation request in the activity table after receiving the message that the update is successful;
and the basic node is used for recording the client information in the basic table according to the activity table.
In a sixth aspect, a client system is provided, the client system comprising an active node, a base node, and a tool node;
the active node is used for acquiring a target query request for querying the client information from the service system; inquiring whether the operation records of the activity table relate to the client in the target inquiry request; when the operation record of the client is inquired in the activity table, sending the inquired operation record of the client to the base node;
the tool node is used for indexing a basic table by using a tool table according to the query field related to the target query request;
the basic node is used for indexing the corresponding customer information record in the basic table according to the tool table; performing data combination according to the inquired operation record of the client and the inquired client information record; and sending the client information record obtained by data combination to the service system.
In a seventh aspect, there is provided a customer information writing apparatus, the apparatus comprising:
the receiving module is used for receiving a target operation request which is sent by a service system and used for operating the client information;
the query module is used for querying whether the operation flow identifier is unique in each operation record of the activity table according to the operation flow identifier carried by the target operation request; wherein, the operation record is used for indicating the historical operation executed by the business system on the client information;
the updating module is used for updating the corresponding index field in the tool table according to the target operation request when the operation pipeline identifier is unique; the tool table is used for indexing the customer information recorded by the basic table;
and the recording module is used for recording the target operation request in the activity table.
In an eighth aspect, there is provided a customer information reading apparatus, the apparatus comprising:
the acquisition module is used for acquiring a target query request for querying the client information from the service system;
the query module is used for querying whether the operation records of the activity table relate to the client in the target query request;
the index module is used for indexing the query field related to the target query request through a tool table when the operation record of the client is queried in the activity table, so as to query the corresponding client information record in the basic table;
the updating module is used for carrying out data combination according to the operation record of the inquired client and the information record of the inquired client;
and the sending module is used for sending the client information record obtained by data combination to the service system.
After receiving a target operation request sent by a service system and used for operating client information, according to an operation flow identifier carried by the target operation request, querying whether the operation flow identifier is unique in each operation record of an activity table, and when the operation flow identifier is unique, updating a corresponding index field for indexing a basic table according to the target operation request in a tool table and recording the target operation request in the activity table. Because the activity table is adopted to record all operations of the service system aiming at the client information, and each operation has a unique operation flow identifier, repeated operation and client data confusion are avoided, the problem of data consistency under the condition of multiple concurrencies is solved, and meanwhile, the performance and the capacity of the system are improved.
Drawings
FIG. 1 is a schematic diagram of a prior art client system;
FIG. 2 is a schematic diagram of a data table;
fig. 3 is a schematic flowchart of a client information writing method according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating another client information writing method according to a second embodiment of the present invention;
fig. 5 is a schematic flowchart of a client information reading method according to a third embodiment of the present invention;
fig. 6 is one of schematic interaction diagrams of nodes in a client system according to a fourth embodiment of the present invention;
fig. 7 is a second schematic view illustrating interaction of nodes in the client system according to the fourth embodiment of the present invention;
FIG. 8 is a schematic illustration of a base table;
fig. 9 is an interaction diagram of each node in the client system according to the fifth embodiment of the present invention;
FIG. 10 is one of schematic diagrams of a client system;
FIG. 11 is a second schematic diagram of a client system;
fig. 12 is a schematic structural diagram of a client information writing apparatus according to a seventh embodiment of the present invention;
fig. 13 is a schematic structural diagram of a client information reading apparatus according to an eighth embodiment of the present invention.
Detailed Description
The embodiments of the present invention will be described in detail with reference to the accompanying drawings.
Example one
To clearly illustrate the method provided by the present embodiment, first, a data table related to the present embodiment is briefly introduced, and fig. 2 is a schematic diagram of the data table, as shown in fig. 2, the data table related to the present embodiment includes:
and the activity table is used for recording the target operation request.
And the basic table is used for recording the client information.
And the tool table is used for indexing the client information table.
The following will describe the client information writing method in detail, and fig. 3 is a schematic flow chart of a client information writing method according to an embodiment of the present invention, and as shown in fig. 3, the method includes:
Specifically, when the business system needs to perform an operation of adding, modifying or deleting the client information, the business system sends an operation request, specifically, the operation request includes an operation flow identifier, and the operation flow identifier is a unique identifier of the operation, that is, each operation has a different operation flow identifier. In addition, the operation request also includes the type of the specific operation, and the operation object, i.e. the field for which the operation is directed. When the specific operation type is addition or modification, the operation request may further include operation content, that is, a field value to be added or modified for the field.
Generally, the amount of client information is huge, in order to perform quick indexing, a client Identifier (ID) of the client information needing to be operated can be carried in an operation request, and the client identifier has uniqueness, so that the query of a client information record can be facilitated.
And 102, inquiring whether the operation flow identifier is unique in each operation record of the activity table according to the operation flow identifier carried by the target operation request.
Wherein the operation record is used for indicating the historical operation executed by the business system on the client information. Specifically, an idempotent function is used to compare the operation flow identifier carried by the target operation request with the operation flow identifier field of each operation record in the activity table, so as to query whether the operation flow identifier is repeated with the operation flow identifier of each operation record in the activity table, thereby avoiding repeated processing of the same target operation request.
Each operation record is recorded in the activity table, and the operation record is used for recording information carried in the operation request, a service system for sending the operation request, sending time and the like.
And 103, when the operation flow identifier is unique, updating the corresponding index field in the tool table according to the target operation request.
The tool table is used for indexing the client information recorded by the basic table. Specifically, the tool table may be a general index table, or may be a unique index table containing some constraints, and is mainly used to accelerate the query speed of the client information table and ensure that the data meets the constraints. For example: handset number or registered mailbox uniqueness. The tool table indexes the index field, and the index field contained in the specific tool table is determined according to the business rule.
Specifically, when the operation flow identifier is unique, it may be determined that no repeated operation occurs, and then the corresponding index field in the tool table is updated according to the target operation request.
If the tool table is a common index table, before updating the corresponding index field in the tool table, checking whether the operation meets the constraint condition, if so, updating the corresponding index field in the tool table, otherwise, returning a message of operation failure to the service system.
If the tool table is the unique index table, whether the operation meets the uniqueness constraint condition or not can be checked in the process of updating the corresponding index field in the tool table, if so, the tool table is updated successfully, otherwise, the tool table is updated unsuccessfully, and a message of operation failure is returned to the service system.
Further, if the operation flow identifier is not unique, it indicates that the activity table already has an operation record corresponding to the target operation request, and processes the request, so that the process may have repeated operations, and ends the process.
And 104, recording the target operation request in the activity table.
Specifically, the relevant information of the target operation request received this time is recorded in the activity table, and a corresponding operation record is generated for subsequent query.
For example: the activity table may include the operation pipeline identifier, the operation type, the operation object, and the operation content carried in the operation request, and the service system and the sending time for sending the operation request.
Therefore, the information recorded by the activity table comprises the operation flow identifier, so that each operation can be conveniently controlled not to be repeatedly processed, namely idempotent, and the traceability of the operation is ensured.
In this embodiment, after receiving a target operation request for operating client information sent by a service system, according to an operation flow identifier carried by the target operation request, whether the operation flow identifier is unique is queried in each operation record of an active table, and when the operation flow identifier is unique, in a tool table, according to the target operation request, a corresponding index field for indexing a base table is updated, and the target operation request is recorded in the active table. Because the activity table is adopted to record all operations of the service system aiming at the client information, and each operation has a unique operation flow identifier, repeated operation and client data confusion are avoided, the problem of data consistency under the condition of multiple concurrencies is solved, and meanwhile, the performance and the capacity of the system are improved.
Example two
To clearly illustrate the previous embodiment, this embodiment further provides another client information writing method, and on the basis of the previous embodiment, further after step 104, the active table and the client information table may be merged, specifically, fig. 4 is a flowchart of another client information writing method provided in the second embodiment of the present invention, and as shown in fig. 4, the method includes:
Specifically, the preset trigger conditions include: satisfying a preset time interval; and/or the condition that the number of the operation records to be merged in the activity table is greater than a preset threshold value is met.
In the method provided in fig. 3, it can be seen that when the service system requests to perform an operation on the client information, the corresponding operation is not performed on the basic table for recording the client information, but the operation is recorded in the activity table. The operation records in the activity table need to be merged when the number of the operation records accumulated in the activity table is enough to be larger than a preset threshold value or at preset time intervals. The operation record to be merged here may be all the operation records in the activity table, or may be a part of the operation records, which is not limited in this embodiment.
Specifically, after the operation records to be merged of each client are respectively obtained from the activity table by taking the client as a unit, for each client, the value of each field in the operation records to be merged of the client is utilized to update the value of the corresponding field of the client in the client information record of the current version in the base table, so as to complete merging of the operation records, and the obtained client information record of the next version is stored in the base table.
Specifically, after the merging is completed for the operation record to be merged, the operation record to be merged is moved from the activity table to the history database. So that when the client data is in disorder, subsequent source tracing query can be carried out.
In this embodiment, after receiving a target operation request for operating client information sent by a service system, according to an operation flow identifier carried by the target operation request, whether the operation flow identifier is unique is queried in each operation record of an active table, and when the operation flow identifier is unique, in a tool table, according to the target operation request, a corresponding index field for indexing a base table is updated, and the target operation request is recorded in the active table. Because the activity table is adopted to record all operations of the service system aiming at the client information, and each operation has a unique operation flow identifier, repeated operation and client data confusion are avoided, the problem of data consistency under the condition of multiple concurrencies is solved, and meanwhile, compared with a locking mechanism, the performance and the capacity of the system are improved.
EXAMPLE III
Fig. 5 is a schematic flow chart of a client information reading method according to a third embodiment of the present invention, where the client information reading method according to this embodiment corresponds to the client information writing method according to the foregoing embodiment, and as shown in fig. 5, the method includes:
Specifically, as a possible implementation form, when the index field of the target query request is the client identifier, the query may be directly performed in the operation record of the active table according to the client identifier, and if the operation record of the client identifier exists, it is determined that the client information of the client recorded in the base table is not the current latest client information, and the update is required according to the queried operation record.
Further, as another possible implementation form, when the index field of the target query request is not the client identifier, the client identifier corresponding to the index field of the target query request may be queried in the tool table. And further querying the operation record of the active table according to the client identifier, and if the operation record of the client identifier exists, determining that the client information of the client recorded in the basic table is not the current latest client information and updating according to the queried operation record.
Specifically, the query field related to the target query request is indexed through a tool table, so that the value of the query field in the client information record of the current version is queried in a basic table.
And step 304, merging data according to the operation records of the inquired clients and the inquired client information records.
Specifically, when the operation record with the client identifier is queried in the active table according to the client identifier in the target query request, the field value corresponding to the client identifier in the client information record of the current version is updated in the basic table by using the field value in the queried operation record.
Further, when the operation record of the client is not inquired in the active table, inquiring the client information record of the current version in the basic table, and further sending the inquired client information record to the service system.
It should be noted that, since the present embodiment is a client information reading method corresponding to the first embodiment, please refer to the related description in the first embodiment for the content that is not described in detail in the present embodiment.
In the process of writing the client information, after receiving a target operation request which is sent by a service system and used for operating the client information, according to an operation flow identifier carried by the target operation request, whether the operation flow identifier is unique in each operation record of an activity table is inquired, and when the operation flow identifier is unique, in a tool table, according to the target operation request, a corresponding index field used for indexing a basic table is updated, and the target operation request is recorded in the activity table. Because the activity table is adopted to record all operations of the service system aiming at the client information, and each operation has a unique operation flow identifier, repeated operation and client data confusion are avoided, the problem of data consistency under the condition of multiple concurrencies is solved, and meanwhile, compared with a locking mechanism, the performance and the capacity of the system are improved.
Correspondingly, in the reading process, a target query request for querying client information is acquired from a service system, whether a client in the target query request is involved in an operation record of an active table is further queried, when the operation record of the client is queried in the active table, a query field involved in the target query request is indexed through a tool table, so that the corresponding client information record is queried in the basic table, data merging is performed according to the queried operation record of the client and the queried client information record, and the client information record obtained by data merging is sent to the service system.
Example four
In order to clearly illustrate the client information writing method provided by the foregoing embodiment, the present embodiment provides an information processing procedure for implementing the client information writing method in an application scenario of a client system. Fig. 6 is one of schematic interaction diagrams of nodes in a client system according to a fourth embodiment of the present invention, where as shown in fig. 6, the client system includes an active node, a base node, and a tool node.
The active node interacts with the service system, the active node is used for maintaining an active table, the basic node is used for maintaining a basic table, and the tool node is used for maintaining a tool table.
As shown in fig. 6, the information processing method includes:
in step 401, the active node obtains a target operation request for operating the client information from the service system.
Wherein the operation record is used for indicating the historical operation executed by the business system on the client information.
Specifically, the active node obtains an operation flow identifier carried by the target operation request, and compares the operation flow identifier with an operation flow identifier field of each operation record in the active table by using an idempotent function, so as to query whether the operation flow identifier is repeated with the operation flow identifier of each operation record in the active table.
And the tool table is used for indexing the client information recorded by the basic table.
Step 404, after receiving the message of successful update, the active node records the target operation request in the active table and returns the operation result to the service system.
It can be seen that when the service system requests to operate on the client information, the corresponding operation is not performed on the basic table for recording the client information, but the operation is recorded in the activity table. The operation records in the activity table need to be merged when the number of the operation records accumulated in the activity table is enough to be larger than a preset threshold value or at preset time intervals. The operation record to be merged here may be all the operation records in the activity table, or may be a part of the operation records, which is not limited in this embodiment.
Specifically, fig. 7 is a second schematic view of interaction between nodes in the client system according to the fourth embodiment of the present invention, as shown in fig. 7:
Specifically, the base node obtains the operation record to be merged of each client from the activity table in units of clients.
And 502, the base node performs data merging according to the operation record to be merged and the client information record of the current version in the base table to obtain the client information record of the next version, and then returns a message of successful merging to the active node.
Specifically, for each client, the base node updates the corresponding field value in the client information record of the client of the current version in the base table by using each field value in the operation record to be merged of the client.
As a possible implementation manner, there are a plurality of fields in the base table, fig. 8 is a schematic diagram of the base table, and as shown in fig. 8, the data content of the base table is numerous, and therefore, the base table needs to be indexed depending on the tool table.
In step 503, the active node moves the operation record to be merged from the active table to the history database according to the message that the merging is successful.
Further, the client system may also include a metadata node.
Based on the method, the tool node acquires the index fields involved in the configured business rules from the metadata node and adds the index fields involved in the business rules to the tool table.
The service rules record the query dimensions followed by the service system when querying the client information, specifically, the query dimensions include each index field and the query fields to be queried, so that the tool node can add the index fields related in the service rules to the tool table, so as to query the basic table quickly and improve the query efficiency.
EXAMPLE five
In order to clearly illustrate the client information reading method provided by the foregoing embodiment, the present embodiment provides an information processing procedure for implementing the client information reading method in an application scenario of a client system. Fig. 9 is an interaction diagram of nodes in a client system according to a fifth embodiment of the present invention, and as shown in fig. 9, the client system includes an active node, a base node, and a tool node.
The active node interacts with the service system, the active node is used for maintaining an active table, the basic node is used for maintaining a basic table, and the tool node is used for maintaining a tool table.
As shown in fig. 9, the information processing method includes:
Further, when the index field of the target query request is not the client identifier, the active node queries the client identifier corresponding to the index field of the target query request in the tool table through the tool node before querying the active table.
Specifically, the base node indexes the query field related to the target query request through a tool table in the tool node, so as to query the value of the query field in the client information record of the current version in the base table.
And step 604, the basic node performs data combination according to the operation record of the inquired client and the inquired client information record, and sends the client information record obtained by data combination to the service system.
Specifically, the active node sends the queried operation record to the base node when querying the operation record with the client identifier in the active table according to the client identifier corresponding to the target query request, so that in the base table, the base node updates the field value corresponding to the client identifier in the client information record of the current version by using the field value in the queried operation record.
Further, when the operation record of the client is not inquired in the active table, the base node inquires the client information record of the current version in the base table; and the basic node sends the inquired customer information record to the service system.
EXAMPLE six
The present embodiment provides a client system, and fig. 10 is a schematic diagram of a client system, as shown in fig. 10, the client system includes an active node, a base node, and a tool node.
The number of the active nodes can be one or more, and each active node interacts with the corresponding service system. The corresponding relationship here may be that the active node corresponds to the service system one to one, or that multiple active nodes correspond to one service system, or that one active node corresponds to multiple service systems.
In order to clearly illustrate the client system, the embodiment provides two possible implementation manners of the corresponding client system in two possible application scenarios.
As a possible implementation manner, in an application scenario in which a service system operates client information, after an active node is configured to obtain a target operation request for operating the client information from the service system, according to an operation flow identifier carried by the target operation request, it is queried whether the operation flow identifier is unique in each operation record of an active table.
Wherein the operation record is used for indicating the historical operation executed by the business system on the client information.
And the tool node is used for updating the corresponding index field in the tool table according to the target operation request and returning a message of successful update to the active node when the active node determines that the operation flow identifier is unique.
And the tool table is used for indexing the client information recorded by the basic table.
And the activity table is further used for recording the target operation request in the activity table after receiving the message of successful update.
And the base node is used for recording the client information in the base table according to the activity table.
Further, the base node is specifically configured to obtain, from the active node, an operation record to be merged in the active table when a preset trigger condition is met; performing data merging according to the operation record to be merged and the client information record of the current version in the basic table to obtain the client information record of the next version; and returning a message of successful combination to the active node.
And the active node is further configured to move the operation record to be merged from the active table to a history database according to the message that the merging is successful.
Further, fig. 11 is a second schematic diagram of the client system, and as shown in fig. 11, the client system further includes: and a metadata node.
And the metadata node is used for configuring the business rule.
Based on the above, the tool node is further configured to obtain, from the metadata node, an index field involved in the configured business rule; and adding the index field involved in the business rule into the tool table.
As another possible implementation manner, in an application scenario where the business system queries the client information, the active node is configured to obtain a target query request for querying the client information from the business system; inquiring whether the operation records of the activity table relate to the client in the target inquiry request; and when the operation record of the client is inquired in the activity table, sending the inquired operation record of the client to the base node.
And the tool node is used for indexing a basic table by using a tool table according to the query field related to the target query request.
The basic node is used for indexing the corresponding customer information record in the basic table according to the tool table; performing data combination according to the inquired operation record of the client and the inquired client information record; and sending the client information record obtained by data combination to the service system.
It can be seen that, after receiving a target operation request sent by a service system for operating client information, according to an operation flow identifier carried by the target operation request, querying whether the operation flow identifier is unique in each operation record of an activity table, and when the operation flow identifier is unique, updating a corresponding index field for indexing a base table according to the target operation request in a tool table, and recording the target operation request in the activity table. Because the activity table is adopted to record all operations of the service system aiming at the client information, and each operation has a unique operation flow identifier, repeated operation and client data confusion are avoided, the problem of data consistency under the condition of multiple concurrencies is solved, and meanwhile, the performance and the capacity of the system are improved.
EXAMPLE seven
Fig. 12 is a schematic structural diagram of a client information writing apparatus according to a seventh embodiment of the present invention, as shown in fig. 12, including: a receiving module 71, a query module 72, an update module 73 and a recording module 74.
The receiving module 71 is configured to receive a target operation request sent by the service system for operating the client information.
And the query module 72 is configured to query whether the operation flow identifier is unique in each operation record of the activity table according to the operation flow identifier carried by the target operation request.
Wherein the operation record is used for indicating the historical operation performed by the business system on the client information.
An updating module 73, configured to update the corresponding index field in the tool table according to the target operation request when the operation pipeline identifier is unique.
The tool table is used for indexing the customer information recorded by the basic table.
A recording module 74, configured to record the target operation request in the activity table.
In this embodiment, after receiving a target operation request for operating client information sent by a service system, according to an operation flow identifier carried by the target operation request, whether the operation flow identifier is unique is queried in each operation record of an active table, and when the operation flow identifier is unique, in a tool table, according to the target operation request, a corresponding index field for indexing a base table is updated, and the target operation request is recorded in the active table. Because the activity table is adopted to record all operations of the service system aiming at the client information, and each operation has a unique operation flow identifier, repeated operation and client data confusion are avoided, the problem of data consistency under the condition of multiple concurrencies is solved, and meanwhile, the performance and the capacity of the system are improved.
Example eight
Fig. 13 is a schematic structural diagram of a client information reading apparatus according to an eighth embodiment of the present invention, and as shown in fig. 13, the apparatus includes: an acquisition module 81, a query module 82, an indexing module 83, an update module 84, and a sending module 85.
The obtaining module 81 is configured to obtain a target query request for querying client information from a service system.
And the query module 82 is used for querying whether the operation record of the activity table relates to the client in the target query request.
And the indexing module 83 is configured to index, when the operation record of the client is queried in the active table, the query field related to the target query request through a tool table, so as to query the corresponding client information record in the base table.
And the updating module 84 is used for carrying out data combination according to the operation record of the inquired client and the information record of the inquired client.
And a sending module 85, configured to send the client information record obtained by data merging to the service system.
In the process of writing the client information, after receiving a target operation request which is sent by a service system and used for operating the client information, according to an operation flow identifier carried by the target operation request, whether the operation flow identifier is unique in each operation record of an activity table is inquired, and when the operation flow identifier is unique, in a tool table, according to the target operation request, a corresponding index field used for indexing a basic table is updated, and the target operation request is recorded in the activity table. Because the activity table is adopted to record all operations of the service system aiming at the client information, and each operation has a unique operation flow identifier, repeated operation and client data confusion are avoided, the problem of data consistency under the condition of multiple concurrencies is solved, and meanwhile, the performance and the capacity of the system are improved.
Correspondingly, in the reading process, a target query request for querying client information is acquired from a service system, whether a client in the target query request is involved in an operation record of an active table is further queried, when the operation record of the client is queried in the active table, a query field involved in the target query request is indexed through a tool table, so that the corresponding client information record is queried in the basic table, data merging is performed according to the queried operation record of the client and the queried client information record, and the client information record obtained by data merging is sent to the service system.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (30)
1. An information processing method based on a client system, wherein the client system includes an active node for maintaining an active table, a base node for maintaining a base table, and a tool node for maintaining a tool table, the method comprising:
the active node acquires a target operation request for operating the client information from a service system;
the active node compares the operation flow identifier carried by the target operation request with the operation flow identifier field of each operation record in the active table by utilizing an idempotent function according to the operation flow identifier carried by the target operation request so as to inquire whether the operation flow identifier is unique or not; wherein, the operation record is used for indicating the historical operation executed by the business system on the client information; the basic node can carry out data combination according to the operation records of the inquired clients and the inquired client information records to obtain combined client information records;
when the active node determines that the operation flow identifier is unique, the tool node updates the corresponding index field in the tool table according to the target operation request and returns a message of successful update to the active node; the tool table is used for indexing the customer information recorded by the basic table;
and after receiving the message of successful update, the active node records the target operation request in the active table.
2. The client system-based information processing method of claim 1, further comprising:
when a preset trigger condition is met, the basic node acquires operation records to be combined in the activity table from the activity node;
the basic node performs data merging according to the operation record to be merged and the client information record of the current version in the basic table to obtain the client information record of the next version;
the base node returns a message of successful combination to the active node;
and the active node moves the operation records to be merged from the active list to a historical database according to the message of successful merging.
3. The client system-based information processing method of claim 2, wherein the base node obtains the operation record to be merged in the activity table from the activity node, and the method comprises:
and the base node respectively acquires the operation records to be merged of each client from the activity table by taking the client as a unit.
4. The client system-based information processing method according to claim 3, wherein the data merging by the base node according to the operation record to be merged and the client information record of the current version in the base table comprises:
and for each client, the basic node updates the corresponding field value in the client information record of the client of the current version in the basic table by using the field value in the operation record to be merged of the client.
5. The client system-based information processing method according to claim 2, wherein the preset trigger condition includes:
satisfying a preset time interval;
and/or the condition that the number of the operation records to be merged in the activity table is greater than a preset threshold value is met.
6. The client-system-based information processing method according to any one of claims 1 to 5, wherein the querying, by the active node, whether the operation flow identifier is unique in each operation record of the active table according to the operation flow identifier carried by the target operation request includes:
and the active node acquires the operation flow identifier carried by the target operation request.
7. The client system-based information processing method according to any one of claims 1 to 5, wherein the client system further includes a metadata node; the method further comprises the following steps:
the tool node acquires an index field related in the configured business rule from the metadata node;
and the tool node adds the index field involved in the business rule to the tool table.
8. An information processing method based on a client system, wherein the client system includes an active node for maintaining an active table, a base node for maintaining a base table, and a tool node for maintaining a tool table, the method comprising:
the active node acquires a target query request for querying client information from a service system;
the active node inquires the operation record of the active table whether the client in the target inquiry request is involved; the operation records comprise historical operations executed by the business system on the customer information and unique operation pipeline identifiers determined by utilizing the idempotent function;
when the operation record of the client is inquired in the activity table, sending the inquired operation record of the client to the base node;
the basic node indexes according to the query field related to the target query request through a tool table in the tool node so as to query the corresponding customer information record in the basic table;
the basic node performs data combination according to the operation records of the inquired clients and the inquired client information records;
and the basic node sends a client information record obtained by data combination to the service system.
9. The client-system-based information processing method of claim 8, wherein the base node indexes, through a tool table in the tool node, according to the query field involved in the target query request, so as to query a corresponding client information record in the base table, and the method comprises:
and the basic node indexes the query field related to the target query request through a tool table in the tool node so as to query the value of the query field in the client information record of the current version in the basic table.
10. The client system-based information processing method of claim 8, wherein after the active node obtains a target query request for querying client information from a service system, the method further comprises:
and when the index field of the target query request is not the customer identification, the active node queries the customer identification corresponding to the index field of the target query request in the tool table through the tool node.
11. The client system-based information processing method according to claim 8, wherein when the operation record of the client is queried in the active table, the base node performs data merging according to the queried operation record of the client and the client information record of the current version in the base table, including:
the active node sends the inquired operation record to the basic node when inquiring the operation record with the client identification in the active table according to the client identification corresponding to the target inquiry request;
in the basic table, the basic node updates the field value corresponding to the client identifier in the client information record of the current version by using the field value in the queried operation record.
12. The client system-based information processing method according to any one of claims 8-11, wherein the active node queries the operation record of the active table to see if the client in the target query request is involved, further comprising:
when the operation record of the client is not inquired in the active table, the base node inquires the client information record of the current version in the base table;
and the basic node sends the inquired customer information record to the service system.
13. A method of writing customer information, the method comprising:
receiving a target operation request which is sent by a service system and used for operating client information;
according to the operation flow identification carried by the target operation request, comparing the operation flow identification carried by the target operation request with the operation flow identification field of each operation record in the activity table by utilizing an idempotent function in each operation record of the activity table so as to inquire whether the operation flow identification is unique or not; wherein, the operation record is used for indicating the historical operation executed by the business system on the client information; the basic node can carry out data combination according to the operation records of the inquired clients and the inquired client information records to obtain combined client information records;
when the operation flow identifier is unique, updating a corresponding index field in a tool table according to the target operation request; the tool table is used for indexing the client information recorded by the basic table;
and recording the target operation request in the activity table.
14. The customer information writing method according to claim 13, further comprising:
when a preset trigger condition is met, acquiring operation records to be combined in the activity list;
performing data merging according to the operation record to be merged and the client information record of the current version in the basic table to obtain the client information record of the next version;
and moving the operation record to be merged from the activity table to a historical database.
15. The method according to claim 14, wherein the obtaining the operation record to be merged in the activity table when a preset trigger condition is satisfied comprises:
and respectively acquiring the operation records to be merged of each client by taking the client as a unit from the activity table.
16. The method according to claim 15, wherein the performing data merging based on the operation record to be merged and the current version of the client information record in the base table comprises:
and for each client, updating the corresponding field value in the client information record of the client of the current version in the basic table by using each field value in the operation record to be merged of the client.
17. The client information writing method according to claim 15, wherein the preset trigger condition includes:
satisfying a preset time interval;
and/or the condition that the number of the operation records to be merged in the activity table is greater than a preset threshold value is met.
18. The client information writing method according to any one of claims 14 to 17, wherein the querying, according to the operation flow identifier carried by the target operation request, whether the operation flow identifier is unique in each operation record of an activity table includes:
acquiring an operation flow identifier carried by the target operation request;
and comparing the operation flow identification with the operation flow identification fields of all the operation records in the activity table by utilizing an idempotent function so as to inquire whether the operation flow identification is repeated with the operation flow identification of all the operation records in the activity table.
19. A method of writing customer information according to any one of claims 14-17, characterized in that the method further comprises:
and adding the index field related in the business rule into the tool table according to the configured business rule.
20. A method for reading customer information, the method comprising:
acquiring a target query request for querying client information from a service system;
querying whether the operation record of the activity table relates to the client in the target query request; the operation record comprises historical operations and operation flow identifiers which are used for indicating the business system to execute on the client information;
when the operation records of the clients are inquired in the active table, the inquiry fields related to the target inquiry requests are indexed through a tool table, so that the corresponding client information records are inquired in a basic table;
performing data combination according to the operation records of the inquired clients and the inquired client information records;
and sending the client information record obtained by data combination to the service system.
21. The client information reading method according to claim 20, wherein when the operation record of the client is queried in the active table, the query field involved in the target query request is indexed by a tool table to query a corresponding client information record in a base table, and the method comprises:
and indexing the query field related to the target query request through the tool table so as to query the value of the query field in the client information record of the current version in the basic table.
22. The client information reading method of claim 20, wherein after obtaining the target query request for querying the client information from the service system, further comprising:
and when the index field of the target query request is not the client identification, querying the client identification corresponding to the index field of the target query request in the tool table.
23. The client information reading method according to claim 20, wherein the data merging based on the operation record of the queried client and the queried client information record comprises:
and according to the client identifier in the target query request, when the operation record with the client identifier is queried in the activity table, updating the field value corresponding to the client identifier in the client information record of the current version by using the field value in the queried operation record in the basic table.
24. The client information reading method according to any one of claims 20 to 23, wherein the querying whether the operation record of the activity table is after the client in the target query request is involved, further comprises:
when the operation record of the client is not inquired in the active table, inquiring the client information record of the current version in the basic table;
and sending the inquired customer information record to the service system.
25. A client system, comprising an active node, a base node, and a tool node;
the active node is used for acquiring a target operation request for operating client information from a service system, and comparing the operation flow identifier carried by the target operation request with the operation flow identifier field of each operation record in an active table by utilizing an idempotent function in each operation record of the active table according to the operation flow identifier carried by the target operation request so as to inquire whether the operation flow identifier is unique or not; wherein, the operation record is used for indicating the historical operation executed by the business system on the client information; the basic node can carry out data combination according to the operation records of the inquired clients and the inquired client information records to obtain combined client information records;
the tool node is used for updating the corresponding index field in the tool table according to the target operation request when the active node determines that the operation flow identifier is unique, and returning a message of successful update to the active node; the tool table is used for indexing the client information recorded by the basic table;
the active node is further configured to record the target operation request in the active table after receiving the message that the update is successful;
and the basic node is used for recording the client information in the basic table according to the activity table.
26. The client system of claim 25,
the base node is specifically configured to obtain, from the active node, an operation record to be merged in the active table when a preset trigger condition is met; performing data merging according to the operation record to be merged and the client information record of the current version in the basic table to obtain the client information record of the next version; returning a message of successful combination to the active node;
and the active node is further configured to move the operation record to be merged from the active table to a history database according to the message that the merging is successful.
27. The client system of claim 25, wherein the client system further comprises: a metadata node;
the metadata node is used for configuring a business rule;
the tool node is further configured to obtain, from the metadata node, an index field involved in the configured business rule; and adding the index field involved in the business rule into the tool table.
28. A client system, comprising an active node, a base node, and a tool node;
the active node is used for acquiring a target query request for querying the client information from the service system; inquiring whether the operation record of the activity table relates to the client in the target inquiry request; when the operation record of the client is inquired in the activity table, sending the inquired operation record of the client to the base node; the operation records comprise historical operations executed by the business system on the customer information and unique operation pipeline identifiers determined by utilizing the idempotent function;
the tool node is used for indexing a basic table by using a tool table according to the query field related to the target query request;
the basic node is used for indexing the corresponding customer information record in the basic table according to the tool table; performing data combination according to the inquired operation record of the client and the inquired client information record; and sending the client information record obtained by data combination to the service system.
29. A client information writing apparatus, characterized in that the apparatus comprises:
the receiving module is used for receiving a target operation request which is sent by a service system and used for operating the client information;
the query module is used for comparing the operation flow identifier carried by the target operation request with the operation flow identifier field of each operation record in the activity table by utilizing an idempotent function in each operation record of the activity table according to the operation flow identifier carried by the target operation request so as to query whether the operation flow identifier is unique; wherein, the operation record is used for indicating the historical operation executed by the business system on the client information; the basic node can carry out data combination according to the operation records of the inquired clients and the inquired client information records to obtain combined client information records;
the updating module is used for updating the corresponding index field in the tool table according to the target operation request when the operation flow identifier is unique; the tool table is used for indexing the client information recorded by the basic table;
and the recording module is used for recording the target operation request in the activity table.
30. A client information reading apparatus, characterized in that the apparatus comprises:
the acquisition module is used for acquiring a target query request for querying the client information from the service system;
the query module is used for querying whether the operation records of the activity table relate to the client in the target query request;
the index module is used for indexing the query field related to the target query request through a tool table when the operation record of the client is queried in the activity table, so as to query the corresponding client information record in a basic table; the operation records comprise historical operations executed by the business system on the customer information and unique operation pipeline identifiers determined by utilizing the idempotent function;
the updating module is used for carrying out data combination according to the operation record of the inquired client and the information record of the inquired client;
and the sending module is used for sending the client information record obtained by data combination to the service system.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611131054.7A CN107016548B (en) | 2016-12-09 | 2016-12-09 | Client system, information processing method, reading and writing method and device |
| CN202210231595.6A CN114677145A (en) | 2016-12-09 | 2016-12-09 | Client system, information processing method, and reading and writing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611131054.7A CN107016548B (en) | 2016-12-09 | 2016-12-09 | Client system, information processing method, reading and writing method and device |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210231595.6A Division CN114677145A (en) | 2016-12-09 | 2016-12-09 | Client system, information processing method, and reading and writing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107016548A CN107016548A (en) | 2017-08-04 |
| CN107016548B true CN107016548B (en) | 2022-01-28 |
Family
ID=59439565
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210231595.6A Pending CN114677145A (en) | 2016-12-09 | 2016-12-09 | Client system, information processing method, and reading and writing method and device |
| CN201611131054.7A Active CN107016548B (en) | 2016-12-09 | 2016-12-09 | Client system, information processing method, reading and writing method and device |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210231595.6A Pending CN114677145A (en) | 2016-12-09 | 2016-12-09 | Client system, information processing method, and reading and writing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN114677145A (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110032598B (en) * | 2018-12-20 | 2020-05-12 | 阿里巴巴集团控股有限公司 | Method and device for updating field and electronic equipment |
| CN111898139B (en) | 2018-12-20 | 2024-04-16 | 创新先进技术有限公司 | Data reading and writing method and device and electronic equipment |
| CN110489438A (en) * | 2019-08-27 | 2019-11-22 | 奇安信科技集团股份有限公司 | A kind of customer action information processing method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102542057A (en) * | 2011-12-29 | 2012-07-04 | 北京大学 | High dimension data index structure design method based on solid state hard disk |
| CN102789475A (en) * | 2012-05-08 | 2012-11-21 | 华为技术有限公司 | Data synchronization method and device for result set cache at server end of database |
| CN103475721A (en) * | 2013-09-12 | 2013-12-25 | 广东电子工业研究院有限公司 | System for updating digital assets and method thereof |
| CN103473239A (en) * | 2012-06-08 | 2013-12-25 | 腾讯科技（深圳）有限公司 | Method and device for updating data of non relational database |
| CN105912687A (en) * | 2016-04-19 | 2016-08-31 | 江苏物联网研究发展中心 | Mass distributed database memory cell |
| CN105915627A (en) * | 2016-05-30 | 2016-08-31 | 北京小米移动软件有限公司 | Service request processing method and service request processing device |
Family Cites Families (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6131096A (en) * | 1998-10-05 | 2000-10-10 | Visto Corporation | System and method for updating a remote database in a network |
| US6856993B1 (en) * | 2000-03-30 | 2005-02-15 | Microsoft Corporation | Transactional file system |
| CN102096623A (en) * | 2009-12-14 | 2011-06-15 | 深圳速浪数字技术有限公司 | Operation log generation method, server and business operational support system |
| CN102486844A (en) * | 2010-12-01 | 2012-06-06 | 金蝶软件（中国）有限公司 | Method and device for processing concurrent data in enterprise resource planning (ERP) system |
| CN102622407B (en) * | 2012-01-29 | 2014-03-26 | 广州亦云信息技术有限公司 | Log file operating system and log file management method |
| CN103237075B (en) * | 2013-04-24 | 2016-07-06 | 广州市动景计算机科技有限公司 | A kind of method of data synchronization, Apparatus and system |
| CN104901927B (en) * | 2014-03-06 | 2019-03-19 | 菜鸟智能物流控股有限公司 | service processing method and device |
| US9633056B2 (en) * | 2014-03-17 | 2017-04-25 | Commvault Systems, Inc. | Maintaining a deduplication database |
| CN104021213B (en) * | 2014-06-20 | 2017-06-16 | 中国银行股份有限公司 | A method and device for merging associated records |
| CN106156070B (en) * | 2015-03-31 | 2019-07-12 | 华为技术有限公司 | A kind of querying method, file mergences method and relevant apparatus |
| CN106156088B (en) * | 2015-04-01 | 2020-02-04 | 阿里巴巴集团控股有限公司 | Index data processing method, data query method and device |
| CN105450730A (en) * | 2015-11-05 | 2016-03-30 | 北京奇虎科技有限公司 | Method and apparatus for processing request from client |
| CN105653695A (en) * | 2015-12-30 | 2016-06-08 | 青岛海尔智能家电科技有限公司 | Concurrent data request processing method and device |
-
2016
- 2016-12-09 CN CN202210231595.6A patent/CN114677145A/en active Pending
- 2016-12-09 CN CN201611131054.7A patent/CN107016548B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102542057A (en) * | 2011-12-29 | 2012-07-04 | 北京大学 | High dimension data index structure design method based on solid state hard disk |
| CN102789475A (en) * | 2012-05-08 | 2012-11-21 | 华为技术有限公司 | Data synchronization method and device for result set cache at server end of database |
| CN103473239A (en) * | 2012-06-08 | 2013-12-25 | 腾讯科技（深圳）有限公司 | Method and device for updating data of non relational database |
| CN103475721A (en) * | 2013-09-12 | 2013-12-25 | 广东电子工业研究院有限公司 | System for updating digital assets and method thereof |
| CN105912687A (en) * | 2016-04-19 | 2016-08-31 | 江苏物联网研究发展中心 | Mass distributed database memory cell |
| CN105915627A (en) * | 2016-05-30 | 2016-08-31 | 北京小米移动软件有限公司 | Service request processing method and service request processing device |
Non-Patent Citations (2)
| Title |
|---|
| HF-Tree:一种闪存数据库的高更新性能索引结构;周大 等;《计算机研究与发展》;20100531;第47卷(第5期);第832-840页 * |
| Merging distributed database summaries;Mounir Bechchi等;《CIKM "07: Proceedings of the sixteenth ACM conference on Conference on information and knowledge management》;20071130;第419-428页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114677145A (en) | 2022-06-28 |
| CN107016548A (en) | 2017-08-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108089893B (en) | Method and device for determining redundant resources, terminal equipment and storage medium | |
| CN113468199B (en) | Index updating method and system | |
| CN107704202B (en) | Method and device for quickly reading and writing data | |
| CN108460041B (en) | Data processing method and device | |
| CN104142954B (en) | A kind of tables of data based on frequency subregion compares update method and device | |
| CN107016548B (en) | Client system, information processing method, reading and writing method and device | |
| CN108399175B (en) | Data storage and query method and device | |
| CN117009453B (en) | Method and system for inquiring customer group list of customers in real time through digital marketing | |
| CN112882647A (en) | Method, electronic device and computer program product for storing and accessing data | |
| CN112579591B (en) | Data verification method, device, electronic equipment and computer readable storage medium | |
| CN104346347A (en) | Data storage method, device, server and system | |
| US10216771B2 (en) | Creating and handling identification for a resource in a configuration database | |
| CN110019444B (en) | Operation request processing method, device, equipment and system | |
| CN113779286B (en) | Method and device for managing graph data | |
| CN112148728B (en) | Method, apparatus and computer program product for information processing | |
| CN103905512B (en) | A kind of data processing method and equipment | |
| CN106131134B (en) | Method and system for merging and deduplicating message content | |
| CN111858609A (en) | Fuzzy query method and device for block chain | |
| CN114374965A (en) | User subscription data processing method, system, device and medium | |
| US20150100545A1 (en) | Distributed database system and a non-transitory computer readable medium | |
| CN109977097B (en) | Network configuration management method and system based on database | |
| US12277172B2 (en) | Graph creation from multiple databases | |
| CN109741180B (en) | Block chain continuous transaction sequence number generation method and device and block chain network node | |
| CN105095283A (en) | Quasi-friend recommending method in social networking system and quasi-friend recommending system in social networking system | |
| CN107315693B (en) | Data storage method and device |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201016 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20201016 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |