CN111026761B - Financial data storage system, processing method and device - Google Patents

Financial data storage system, processing method and device Download PDF

Info

Publication number
CN111026761B
CN111026761B CN201911269419.6A CN201911269419A CN111026761B CN 111026761 B CN111026761 B CN 111026761B CN 201911269419 A CN201911269419 A CN 201911269419A CN 111026761 B CN111026761 B CN 111026761B
Authority
CN
China
Prior art keywords
data
cache
access
financial data
accessed
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
Application number
CN201911269419.6A
Other languages
Chinese (zh)
Other versions
CN111026761A (en
Inventor
吴越磊
施鹏程
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Jingqian Financial Information Service Co ltd
Original Assignee
Shanghai Jingqian Financial Information Service Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shanghai Jingqian Financial Information Service Co ltd filed Critical Shanghai Jingqian Financial Information Service Co ltd
Priority to CN201911269419.6A priority Critical patent/CN111026761B/en
Publication of CN111026761A publication Critical patent/CN111026761A/en
Application granted granted Critical
Publication of CN111026761B publication Critical patent/CN111026761B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22Indexing; Data structures therefor; Storage structures
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21Design, administration or maintenance of databases
    • G06F16/217Database tuning
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2455Query execution
    • G06F16/24552Database cache management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • Computational Linguistics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Memory System Of A Hierarchy Structure (AREA)

Abstract

The embodiment of the application discloses a financial data storage system, which comprises a database and a buffer module, wherein the database can store financial data related to financial business, and the access frequency of some financial data is more frequent than that of transaction, so that users can access the financial data frequently to cause access of massive users. Thus, to avoid over-accessing the database, financial data having an access frequency above a first threshold may be stored in the cache module. Because the access priority of the cache module is higher than that of the database, once a large number of access requests are met, the cache module is accessed firstly instead of the database, so that the access pressure of the database is reduced, reaction delay or downtime of the database due to the excessively high access amount is avoided, the access efficiency is improved, and the throughput of a storage system is improved.

Description

Financial data storage system, processing method and device
Technical Field
The present disclosure relates to the field of data processing, and in particular, to a storage system, a processing method and a device for financial data.
Background
For financial systems, the frequency of querying data is more frequent than the transaction. Users often view product information, asset information, etc., and most of this data will change only after the transaction has occurred.
The data involved in a financial system is stored in a database, however, database resources are very scarce, exposing the database directly to application service calls is very dangerous, and even a distributed database is not affordable to access by a large number of users. Upon encountering a large number of data requests, the database reaction delays or downtime, which causes a series of catastrophic reactions.
Disclosure of Invention
In order to solve the technical problems, the application provides a financial data storage system, a processing method and a processing device, which can reduce access pressure of a database, avoid response delay or downtime of the database caused by overhigh access quantity, improve access efficiency and improve throughput of the storage system.
In a first aspect, an embodiment of the present application provides a storage system for financial data, where the storage system includes a database and a cache module:
the database is used for storing financial data involved in financial business;
the cache module is used for storing financial data with access frequency higher than a first threshold value in the financial data, and the access priority of the cache module is higher than that of the database.
Optionally, the cache module includes a distributed cache, and the distributed cache is disposed on the cluster server.
Optionally, the cache module includes a distributed cache and a local cache:
the distributed cache is arranged on the cluster server and is used for storing financial data with access frequency higher than a first threshold value and lower than a second threshold value in the financial data;
the local cache is arranged on the application server and is used for storing financial data with access frequency higher than the second threshold value in the financial data, and the access priority of the local cache is higher than that of the distributed cache.
Optionally, the financial data stored in the buffer module is provided with a buffer expiration time, and the buffer expiration time is determined according to the access frequency of the financial data.
Optionally, the financial data stored in the buffer module is updated according to a preset rule, and the preset rule is determined according to the access frequency of the financial data.
Optionally, the storage system further includes a cache management tool:
the cache management tool is used for displaying the data to be identified in the cache module so as to position the cache problem according to the data to be identified.
In a second aspect, an embodiment of the present application provides a method for processing financial data, where a storage system for financial data includes a database and a cache module; the database is used for storing financial data involved in financial business; the cache module is used for storing financial data with access frequency higher than a first threshold value in the financial data, and the access priority of the cache module is higher than that of the database; the method comprises the following steps:
acquiring a data access request, wherein the data access request comprises a data identifier to be accessed;
accessing the cache module according to the data identifier to be accessed;
and if the data identifier to be accessed is hit in the cache module, returning financial data corresponding to the data identifier to be accessed.
Optionally, the method further comprises:
and if the data identifier to be accessed is not hit in the cache module, accessing the database.
Optionally, the cache module includes a distributed cache, and the distributed cache is disposed on the cluster server.
Optionally, the cache module includes a distributed cache and a local cache, and an access priority of the local cache is higher than an access priority of the distributed cache:
the accessing the cache module according to the data identifier to be accessed comprises:
accessing the local cache;
and if the data identifier to be accessed is not hit in the local cache, accessing the distributed cache.
In a third aspect, an embodiment of the present application provides a financial data processing apparatus, including:
the data access method comprises an acquisition unit, a data access unit and a data processing unit, wherein the acquisition unit is used for acquiring a data access request, and the data access request comprises a data identifier to be accessed;
the access unit is used for accessing the cache module according to the data identification to be accessed;
and the return unit is used for returning the data corresponding to the data identifier to be accessed if the data identifier to be accessed is hit in the cache module.
Optionally, the access unit is further configured to:
and if the data identifier to be accessed is not hit in the cache module, accessing the database.
Optionally, the cache module includes a distributed cache, and the distributed cache is disposed on the cluster server.
Optionally, the cache module includes a distributed cache and a local cache, and an access priority of the local cache is higher than an access priority of the distributed cache:
the access unit is used for:
accessing the local cache;
and if the data identifier to be accessed is not hit in the local cache, accessing the distributed cache.
According to the technical scheme, the embodiment of the application has the following advantages:
the financial data storage system provided by the embodiment of the application comprises a database and a cache module, wherein the database can store financial data involved in financial business, and the access frequency of some financial data is more frequent than that of transaction, so that users can access the financial data frequently, and massive users can access the financial data. Thus, to avoid over-accessing the database, financial data having an access frequency above a first threshold may be stored in the cache module. Because the access priority of the cache module is higher than that of the database, once a large number of access requests are met, the cache module is accessed firstly instead of the database, so that the access pressure of the database is reduced, reaction delay or downtime of the database due to the excessively high access amount is avoided, the access efficiency is improved, and the throughput of a storage system is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive faculty for a person skilled in the art.
FIG. 1 is a block diagram of a financial data storage system according to an embodiment of the present application;
FIG. 2 is a block diagram of a financial data storage system according to an embodiment of the present application;
FIG. 3 is a diagram illustrating an exemplary visual interface of a cache management tool according to an embodiment of the present application;
FIG. 4 is a flowchart of a method for processing financial data according to an embodiment of the present disclosure;
fig. 5 is a block diagram of a financial data processing device according to an embodiment of the present application.
Detailed Description
Embodiments of the present application are described below with reference to the accompanying drawings.
The financial data storage system, the financial data processing method and the related device are used for reducing the access pressure of the database, avoiding the response delay or downtime caused by the excessively high access quantity of the database and improving the access efficiency.
Next, a detailed description will be given of a storage system for financial data provided in an embodiment of the present application with reference to the accompanying drawings. Referring to fig. 1, the storage system includes a database 101 and a cache module 102:
the database 101 is used for storing financial data involved in financial transactions.
In this embodiment, the financial data includes configuration information of a storage system of the financial data, registration information of a user (e.g., certificate type, city information, etc.), product information (e.g., product stock, etc.), asset information (e.g., remaining asset, asset transfer information, etc.), and the like.
The cache module 102 is configured to store financial data with an access frequency higher than a first threshold value in the financial data, where an access priority of the cache module 102 is higher than an access priority of the database 101.
It should be noted that, among various financial data, some financial data are of interest to the user, and the frequency of variation is low, so that a massive number of users may access the financial data frequently, while some financial data users are not of interest, and the access frequency may be low. Therefore, in the present embodiment, in order to avoid the database 101 from being excessively accessed, financial data having an access frequency higher than the first threshold may be stored in the cache module 102. Because the access priority of the cache module 102 is higher than that of the database 101, once a large number of access requests are encountered, the cache module 102 is accessed firstly instead of the database 101, so that the access pressure of the database 101 is reduced, the response delay or downtime of the database 101 caused by the excessively high access amount is avoided, and the access efficiency is improved.
For example, configuration information of the storage system, registration information of the user (such as certificate type, city information, etc.) and the like are relatively fixed financial data, which are of little interest to the user, and which may be stored in the database 101; while the user may be very interested in product information (e.g., product inventory, product attributes, etc.), asset information (e.g., remaining assets, asset transfer information, etc.), etc., the user may browse the product information for many products to determine which product to purchase, which results in a relatively high frequency of access to the financial data, which may be stored in the cache module 102.
In one possible implementation, the cache module 102 includes a distributed cache 1021, where the distributed cache 1021 is disposed on a cluster server to separate business applications. The distributed cache 1021 may include a variety of types, and may be, for example, a remote dictionary service (Remote Dictionary Server, redis) or memcached (a distributed cache system).
In one possible implementation, since distributed cache 1021 is actually a remote distributed cache, network overhead is required, which is greater when its access volume is greater. Therefore, in order to reduce the access pressure of the remote cache and reduce the network overhead, the local cache may also be set on the basis of the distributed cache, that is, the cache module 102 includes the distributed cache 1021 and the local cache 1022. At this time, the storage system of the financial data may be referred to as shown in fig. 2.
The distributed cache 1021 is disposed on the cluster server and is used as a first-layer cache for storing financial data with access frequency higher than a first threshold and lower than a second threshold. The local buffer 1022 is disposed on the application server, and is used as a second layer buffer for storing financial data with access frequency higher than a second threshold, where the access priority of the local buffer 1022 is higher than that of the distributed buffer 1021. The local cache 1022 may be ehcache (which is a pure Java in-process cache framework).
The local cache 1022 mainly refers to a cache policy built in the application service, and has the greatest advantage that the application and the cache are in the same process, so that the financial data in the local cache is obtained very efficiently, and no network overhead is basically caused. For particularly hot data, the local cache 1022 is distributed in the application layer because the local cache 1022 does not need remote call, so that the problem can be relieved, the access pressure of the remote cache is reduced, and the network overhead is reduced.
The financial data storage system provided by the embodiment of the application comprises a database and a cache module, wherein the database can store financial data involved in financial business, and the access frequency of some financial data is more frequent than that of transaction, so that users can access the financial data frequently, and massive users can access the financial data. Thus, to avoid over-accessing the database, financial data having an access frequency above a first threshold may be stored in the cache module. Because the access priority of the cache module is higher than that of the database, once a large number of access requests are met, the cache module is accessed firstly instead of the database, so that the access pressure of the database is reduced, reaction delay or downtime of the database due to the excessively high access amount is avoided, the access efficiency is improved, and the throughput of a storage system is improved.
It will be appreciated that, in order to increase the usage of the cache module 102, the cache expiration time needs to be set in the cache module 102, that is, the financial data stored in the cache module 102 is set with the cache expiration time. In order to ensure that the set buffer expiration time is reasonably set and avoid excessive buffer expiration at the same time, the buffer expiration time can be determined according to the access frequency of the financial data. Typically, the higher the frequency of access to the financial data, the shorter its cache expiration time.
It should be noted that, since the financial data may be changed, for example, the product stock may be changed along with the generation of the financial transaction, in order to ensure that the user can browse accurate data after accessing the cache module 102, the financial data stored in the cache module 102 is updated according to a preset rule, where the preset rule is determined according to the access frequency of the financial data.
For example, some financial data have higher access frequency, and users have higher requirements on real-time performance of the financial data, such as the data of the asset condition, transaction detail condition and the like of the users. For the scenario with high real-time requirement, the user transaction needs to update the own asset condition and transaction detail condition data immediately after the completion of the update of the database 101, and the financial data in the cache module 102 should be updated immediately at this time, i.e. the preset rule is updated immediately after the completion of the transaction.
For some financial data, the access frequency is relatively low, and the real-time requirement of the user on the financial data is not high, in this case, in order to avoid causing larger pressure under the condition of larger access concurrency, a strategy of timing update can be adopted, that is, the preset rule is to update according to a preset period, and the size of the preset period can be set according to the real-time requirement of the user. In this case, the update frequency of the financial data is not high, the user's requirement is not high, and the data pre-integration can be performed when the data is cached. Because of low real-time, the pre-integrated financial data is read faster, and in general, the method can be applied to statistical financial data scenes.
Therefore, in this embodiment, for access scenarios with different frequencies, different cache update policies are applied, so that application performance is effectively improved.
It can be appreciated that after the financial data is cached by the cache module 102, the financial data in the cache module 102 can be visually managed, so that the cache problem can be accurately located when an accident occurs in the cache module 102. To this end, the storage system further comprises a cache management tool 103, see fig. 2. When an event occurs, the cache management tool 103 may present the data to be identified in the cache module 102 to locate a cache problem based on the data to be identified. Wherein the data to be identified is determined based on a key value.
The visual interface of the cache management tool 103 may be shown in fig. 3, and when the event occurs, a technician may input a cache key value corresponding to the data to be identified, which may have an error, in the "cache key input box" in the interface, and click on "query" so as to display the data to be identified (i.e. the cache data in fig. 3). The technician can accurately position the cache problem according to the displayed data to be identified.
Based on the storage system of the financial data shown in fig. 1, the embodiment of the application further provides a processing method of the financial data, referring to fig. 4, the method includes:
s401, acquiring a data access request, wherein the data access request comprises a data identifier to be accessed.
S402, accessing the cache module according to the data identification to be accessed.
S403, if the data identifier to be accessed is hit in the cache module, returning the data corresponding to the data identifier to be accessed.
When a user needs to access certain or some financial data in the storage system, the user triggers a data access request through the corresponding terminal equipment, wherein the data access request comprises a data identifier to be accessed, and the data identifier to be accessed is used for identifying the financial data which the user wants to access. After the terminal equipment of the user acquires the data access request, the financial data in the cache module is accessed firstly because the access priority of the cache module is higher than that of the database, and if the data identification to be accessed is hit in the cache module, the financial data corresponding to the data identification to be accessed is returned. If the data identification to be accessed is not hit in the cache module, the database is accessed.
The cache module may include various setting manners. For example, the cache module may include a distributed cache disposed on the cluster server. For another example, the cache module includes a distributed cache and a local cache, where an access priority of the local cache is higher than an access priority of the distributed cache, and the local cache is disposed inside the application service.
When the cache module includes a distributed cache and a local cache, the mode of accessing the cache module according to the data identifier to be accessed in S402 may be to access the local cache preferentially, and if the data identifier to be accessed is not hit in the local cache, access the distributed cache again. Thereby reducing access pressure of remote cache and network overhead.
Based on the method for processing financial data provided in the corresponding embodiment of fig. 4, this embodiment also provides a device for processing financial data, referring to fig. 5, where the device includes:
an obtaining unit 501, configured to obtain a data access request, where the data access request includes a data identifier to be accessed;
an accessing unit 502, configured to access the cache module according to the to-be-accessed data identifier;
and a returning unit 503, configured to return data corresponding to the data identifier to be accessed if the data identifier to be accessed is hit in the cache module.
Optionally, the access unit is further configured to:
and if the data identifier to be accessed is not hit in the cache module, accessing the database.
Optionally, the cache module includes a distributed cache, and the distributed cache is disposed on the cluster server.
Optionally, the cache module includes a distributed cache and a local cache, and an access priority of the local cache is higher than an access priority of the distributed cache:
the access unit is used for:
accessing the local cache;
and if the data identifier to be accessed is not hit in the local cache, accessing the distributed cache.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware related to program instructions, where the above program may be stored in a computer readable storage medium, and when the program is executed, the program performs steps including the above method embodiments; and the aforementioned storage medium may be at least one of the following media: read-only memory (ROM), RAM, magnetic disk or optical disk, etc., which can store program codes.
It should be noted that, in the present specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment is mainly described in a different point from other embodiments. In particular, for the apparatus and system embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, with reference to the description of the method embodiments in part. The apparatus and system embodiments described above are merely illustrative, in which elements illustrated as separate elements may or may not be physically separate, and elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The foregoing is merely one specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (5)

1. A storage system for financial data, the storage system comprising a database and a cache module: the database is used for storing financial data involved in financial business; the cache module is used for storing financial data with access frequency higher than a first threshold value in the financial data, and the access priority of the cache module is higher than that of the database; the cache module comprises a distributed cache and a local cache: the distributed cache is arranged on the cluster server and is used for storing financial data with access frequency higher than a first threshold value and lower than a second threshold value in the financial data;
the local cache is arranged on the application server and is used for storing financial data with access frequency higher than the second threshold value in the financial data, and the access priority of the local cache is higher than that of the distributed cache;
the financial data stored in the cache module is provided with a cache expiration time, and the cache expiration time is determined according to the access frequency of the financial data;
the storage system further comprises a cache management tool, wherein the cache management tool is used for displaying the data to be identified in the cache module so as to locate the cache problem according to the data to be identified.
2. The storage system of claim 1, wherein the financial data stored in the cache module is updated according to a predetermined rule, the predetermined rule being determined according to an access frequency of the financial data.
3. A method of processing financial data, characterized in that it is based on a storage system for financial data according to any one of claims 1-2; the method comprises the following steps: acquiring a data access request, wherein the data access request comprises a data identifier to be accessed;
accessing the cache module according to the data identifier to be accessed;
if the data identifier to be accessed is hit in the cache module, returning financial data corresponding to the data identifier to be accessed;
the accessing the cache module according to the data identifier to be accessed comprises: accessing the local cache; and if the data identifier to be accessed is not hit in the local cache, accessing the distributed cache.
4. A method according to claim 3, characterized in that the method further comprises: and if the data identifier to be accessed is not hit in the cache module, accessing the database.
5. A financial data processing apparatus, characterized in that it is based on a storage system for financial data according to any one of claims 1-2, said apparatus comprising: the data access method comprises an acquisition unit, a data access unit and a data processing unit, wherein the acquisition unit is used for acquiring a data access request, and the data access request comprises a data identifier to be accessed;
the access unit is used for accessing the cache module according to the data identification to be accessed;
a return unit, configured to return data corresponding to the data identifier to be accessed if the data identifier to be accessed is hit in the cache module;
the accessing the cache module according to the data identifier to be accessed comprises: accessing the local cache; and if the data identifier to be accessed is not hit in the local cache, accessing the distributed cache.
CN201911269419.6A 2019-12-11 2019-12-11 Financial data storage system, processing method and device Active CN111026761B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911269419.6A CN111026761B (en) 2019-12-11 2019-12-11 Financial data storage system, processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911269419.6A CN111026761B (en) 2019-12-11 2019-12-11 Financial data storage system, processing method and device

Publications (2)

Publication Number Publication Date
CN111026761A CN111026761A (en) 2020-04-17
CN111026761B true CN111026761B (en) 2024-04-02

Family

ID=70206116

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911269419.6A Active CN111026761B (en) 2019-12-11 2019-12-11 Financial data storage system, processing method and device

Country Status (1)

Country Link
CN (1) CN111026761B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111930719B (en) * 2020-08-13 2023-09-19 中国工商银行股份有限公司 Database access method, device and system
CN112015674B (en) * 2020-08-27 2023-05-30 平安科技(深圳)有限公司 Multi-level-based cache resource access method and device and computer equipment
CN112751912B (en) * 2020-12-15 2021-12-03 北京金山云网络技术有限公司 Configuration adjustment method and device and electronic equipment

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102117248A (en) * 2011-03-09 2011-07-06 浪潮(北京)电子信息产业有限公司 Caching system and method for caching data in caching system
CN107231395A (en) * 2016-03-25 2017-10-03 阿里巴巴集团控股有限公司 Date storage method, device and system
CN108984130A (en) * 2018-07-25 2018-12-11 广东浪潮大数据研究有限公司 A kind of the caching read method and its device of distributed storage

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102117248A (en) * 2011-03-09 2011-07-06 浪潮(北京)电子信息产业有限公司 Caching system and method for caching data in caching system
CN107231395A (en) * 2016-03-25 2017-10-03 阿里巴巴集团控股有限公司 Date storage method, device and system
CN108984130A (en) * 2018-07-25 2018-12-11 广东浪潮大数据研究有限公司 A kind of the caching read method and its device of distributed storage

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
段春梅 ; .云计算分布式缓存技术在海量数据处理平台中的应用.智能计算机与应用.2016,(01),全文. *

Also Published As

Publication number Publication date
CN111026761A (en) 2020-04-17

Similar Documents

Publication Publication Date Title
CN111026761B (en) Financial data storage system, processing method and device
CN110019292B (en) Data query method and device
CN111506559B (en) Data storage method, device, electronic equipment and storage medium
EP3238421B1 (en) System for high-throughput handling of transactions in data-partitioned, distributed, relational database management system
CN109885786B (en) Data caching processing method and device, electronic equipment and readable storage medium
US20180329921A1 (en) Method and apparatus for storing time series data
CN110162512B (en) Log retrieval method, device and storage medium
CN111475519B (en) Data caching method and device
CN105512283A (en) Data quality management and control method and device
US20200364143A1 (en) Externalized configurations and caching solution
US20240045862A1 (en) System and method for efficient processing and managing of reports data and metrics
CN111104401A (en) System and method for storing data in array and linked list based integrated structure
US7610293B2 (en) Correlation of resource usage in a database tier to software instructions executing in other tiers of a multi tier application
CN109785867A (en) Double record process configuration methods, device, computer equipment and storage medium
CN112860746B (en) Cache reduction-based method, equipment and system
CN114490719A (en) Data query method and device, electronic equipment and storage medium
CN114185898A (en) Data query method and device and terminal equipment
CN110196877B (en) Data display method, device, computer equipment and storage medium
CN111131393A (en) User activity data statistical method, electronic device and storage medium
CN116382924B (en) Recommendation method and device for resource allocation, electronic equipment and storage medium
CN116991882B (en) Query optimization method and device based on service priority and electronic equipment
US8626746B2 (en) Tracking modifications to values of various fields in a database serve
US20240013116A1 (en) Method and Apparatus for Providing Cloud Service, and Device
CN117235161A (en) Interface concurrency control method, device, equipment and storage medium
CN114116786A (en) Data processing 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
GR01 Patent grant
GR01 Patent grant