CN115563224A - Distributed parameter caching system - Google Patents
Distributed parameter caching system Download PDFInfo
- Publication number
- CN115563224A CN115563224A CN202211469823.XA CN202211469823A CN115563224A CN 115563224 A CN115563224 A CN 115563224A CN 202211469823 A CN202211469823 A CN 202211469823A CN 115563224 A CN115563224 A CN 115563224A
- Authority
- CN
- China
- Prior art keywords
- unit
- parameter
- file
- interface
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012423 maintenance Methods 0.000 claims description 54
- 238000007689 inspection Methods 0.000 claims description 32
- 238000012545 processing Methods 0.000 claims description 16
- 238000000034 method Methods 0.000 claims description 12
- 230000008569 process Effects 0.000 claims description 11
- 230000004069 differentiation Effects 0.000 claims description 6
- 238000013475 authorization Methods 0.000 claims description 3
- 238000012508 change request Methods 0.000 claims description 3
- 238000012937 correction Methods 0.000 claims description 3
- 239000002699 waste material Substances 0.000 abstract description 3
- 230000008859 change Effects 0.000 abstract description 2
- 230000004044 response Effects 0.000 abstract description 2
- 230000007547 defect Effects 0.000 abstract 1
- 230000006870 function Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 238000012544 monitoring process Methods 0.000 description 5
- 238000012360 testing method Methods 0.000 description 4
- 238000012217 deletion Methods 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- 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
- G06F16/24552—Database cache management
-
- 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/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
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)
- Computing Systems (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a distributed parameter cache system, which is applied to a service node in an embedded manner, does not need independent service deployment, adopts two modes of time-wheel timing pull and consumption response pull of MQ messages of parameter change, efficiently and quickly ensures the consistency, the real-time property and the light weight of parameter cache, does not have various defects caused by network flash and IP switching, supports various data structures, reasonably utilizes memory space and does not have resource waste.
Description
Technical Field
The invention relates to the technical field of parameter caching, in particular to a distributed parameter caching system.
Background
In the existing distributed cache technology, a service cluster needs to be independently deployed, the automatic fault tolerance and recovery functions are poor, the failure of the front-end part reading request is caused by the downtime of a host computer and a slave computer, and the recovery can be realized only by waiting for the restart of a cache service node or the manual switching of a front-end IP. In addition, the host downtime and the deployment of data are not synchronized to the slave machines, the problem of inconsistent data is also introduced by switching the IP, the availability of the system is reduced, online capacity expansion is difficult to support, the online capacity expansion is complicated when the cluster capacity reaches the upper limit, and in order to avoid the problem, operation and maintenance personnel must ensure enough space when the system is on line, which causes great waste on resources.
Disclosure of Invention
The invention provides a distributed parameter caching system applied to a credit card core transaction system. The system solves the problems that in the prior art, due to unitization, each unit data and the service are managed separately, some services need centrally managed data, but cannot be accessed across units. The invention realizes public and private parameter reading in each unitized application service of the distributed system, and ensures efficient and consistent access.
The invention adopts the following technical scheme:
a distributed parameter cache system is used as a middle layer of a public parameter platform, the upper layer is a comprehensive operation platform, and the lower layer is a service module;
the distributed parameter caching system comprises a core framework, an SDK parameter caching module and a file increment processing module; wherein,
the core framework is used for carrying out service initialization on the distributed parameter cache system;
the SDK parameter caching module is used for providing various calling parameters for a service party;
the file increment processing module is used for interfacing with an upper comprehensive operation platform to determine a file format.
Further, the core framework provides 4 interfaces for the comprehensive operation platform, which are respectively an inquiry interface, an inspection interface, a maintenance interface and a disassembly submission interface.
Further, the core framework comprises a maintenance interface unit, a check interface unit, a query interface unit, an interface default implementation unit, an execution flow unit, a batch submission unit, a split submission unit and an analysis log unit, wherein,
the maintenance interface unit, the inspection interface unit and the query interface unit are respectively used for executing the maintenance, inspection and query work of the interface,
the interface default realization unit and the execution flow unit are used for realizing the interface function,
the batch submitting unit and the splitting submitting unit are respectively used for realizing batch submitting and splitting submitting of the request,
the analysis log unit is used for performing log analysis according to the data docked with the comprehensive operation platform.
Further, the SDK parameter caching module includes an MQ instruction monitoring unit, a timing query unit, and a parameter caching unit, where the MQ instruction monitoring unit is configured to monitor an instruction issued by a core frame, the timing query unit is configured to refresh a cache in real time by means of a time wheel, and the parameter caching unit is configured to cache an integrated parameter.
Furthermore, the file increment processing module comprises a file acquisition unit, a file analysis unit, a file comparison unit and a differentiation processing unit, wherein,
the file obtaining unit is used for receiving files from the comprehensive operation platform according to file increment requests, the file analyzing unit is used for analyzing the files received from the comprehensive operation platform, the file comparing unit is used for comparing the analyzed files with files in a database DB, and the differentiation processing unit is used for maintaining differentiation data with different comparison results again.
Further, the core framework further includes a service initialization unit, which is used for initializing the implementation class of the service when the service is started, binding the service to a corresponding execution flow, and binding the service to be stored in a warehouse after the relevant inspection flow is executed.
Further, the file increment processing module is used for processing public parameter change requests in batch, regularly pulling files from the comprehensive operation platform according to preset time, realizing file format analysis, and providing unified file increment data comparison correction and database dropping operation.
Further, the comprehensive operation platform sends the FORM request to a maintenance interface, judges the parameter type specified in the same FORM according to commit data carried in the FORM request, performs splitting operation, and transmits a batch of splitting requests and splitting completion instructions after splitting to a batch submitting unit, wherein the same batch of splitting requests have the same batch number; the FORM request comprises card issuing parameters, limit parameters, authorization parameters and batch parameters.
Further, after receiving the splitting completion instruction sent by the integrated operation platform, the batch submitting unit records the submitted request in a log table of the database DB, analyzes the logs of the same batch in the split log, and calls the maintenance interface.
Further, the core framework is connected to a configuration center, and the configuration center is configured to support business inspection, maintenance inspection, and process configuration of the common parameters, and process the common parameters that are not configured according to default inspection and process.
Through the embodiment of the invention, the following technical effects can be obtained:
(1) The SDK provides approximate local reading of the parameters, the calling is convenient, the user can not sense the parameters, the parameters are cached in the local node, and the performance is obviously higher than that of real-time remote calling.
(2) By updating the core frame type maintenance parameters, unified log splitting, analysis, library falling, query and maintenance and batch operation are provided, default realization of various service parameters is provided, and development is not needed even if the types of the service group parameters are different, and the service group parameters can be directly used.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed in the embodiments or the prior art descriptions will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without inventive labor.
FIG. 1 is a general architecture diagram of applications;
FIG. 2 is a schematic diagram of the relationship between modules in a distributed parameter caching system;
FIG. 3 is a schematic flow diagram of splitting a commit and analyze log.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without inventive efforts based on the embodiments of the present invention, shall fall within the scope of protection of the present invention.
Before describing the technical solution of the present invention in detail, the term convention used in the present invention is first introduced as follows:
distributed: the distributed system is an expandable system structure which is different from the original system structure which adopts a single server to run and store, and utilizes a plurality of servers to share operation and storage load, thereby not only solving the bottleneck problem of the single storage server in the traditional centralized storage system, but also improving the reliability, the availability and the expansibility of the system.
A comprehensive operation platform: and the external system is used for carrying out view-oriented management on the parameters and submitting the common parameters SDK by the form through the current platform.
Parameter caching: and caching the parameters through an internal cache frame.
A file service platform: and managing the files and providing file uploading and downloading functions.
: the common parameter platform provides calling parameters for the service party.
Time wheel: an efficient implementation of similar timing tasks.
Fig. 1 is a general architecture diagram of each application. The distributed parameter cache system is used as a middle layer of the comprehensive operation platform and the service platform, plays a role in starting and stopping, the upper layer is the comprehensive operation platform, and the lower layer is the service module. A core framework in the distributed parameter cache system provides 4 interfaces for a comprehensive operation platform, wherein the interfaces are an inquiry interface, an inspection interface, a maintenance interface and a splitting and submitting interface, the comprehensive operation platform splits the same FORM FORM into a plurality of FORMs, and a public parameter platform is called by multiple requests.
The distributed parameter caching system comprises a core framework, an SDK parameter caching module and a file increment processing module. The relationship of the modules in the distributed parameter caching system is shown in fig. 2.
The core frame is used for carrying out service initialization on the distributed parameter cache system, the maintenance, inspection and query work of the interface is executed by the maintenance interface unit, the inspection interface unit and the query interface unit respectively, the interface function is realized by the interface default realization unit and the execution flow unit, the batch and split submission of the request are realized by the batch submission unit and the split submission unit respectively, and the log analysis is carried out by the log analysis unit according to the data butted with the comprehensive operation platform;
the SDK parameter caching module is used for providing various calling parameters for a service party, monitoring an instruction issued by the core frame through the MQ instruction monitoring unit, refreshing the cache in real time by the timing query unit in a time wheel mode, and caching the integrated parameters into the parameter caching unit;
the file increment processing module is used for determining a file format with the comprehensive operation platform, receiving a file from the comprehensive operation platform according to a file increment request by the file acquisition unit, analyzing the file received from the comprehensive operation platform by the file analysis unit, comparing the analyzed file with a file in the database DB by the file comparison unit, and maintaining different differentiated data with different comparison results again by the differentiation processing unit.
In the core framework, the service initialization unit is used for initializing the implementation class of the service when the service is started, binding the service with a corresponding execution flow, and binding and storing the service after the execution of a relevant inspection flow. And the execution flow unit executes the operation according to the bound execution flow.
The core framework is connected with a configuration center, the configuration center is used for supporting the business inspection, the maintenance inspection and the process configuration of the public parameters, and the configuration center processes the public parameters which are not configured according to the default inspection and the process.
The SDK parameter caching module is provided for a service party to obtain a parameter JAR packet, and two functions realized by the SDK parameter caching module comprise:
(1) And (4) query function: acquiring a parameter result set in a non-differentiated manner by inquiring a parameter API according to a given parameter;
(2) A refreshing function: and refreshing the parameter local cache according to the MQ instruction obtained by monitoring or refreshing the parameter local cache according to the time wheel.
The file incremental processing module processes public parameter change requests in batch, acquires files from the comprehensive operation platform regularly according to preset time, realizes file format analysis, and provides unified file incremental data comparison correction and database dropping operation.
FIG. 3 is a schematic flow diagram of splitting a commit and analyze log. The comprehensive operation platform sends a FORM request to a maintenance interface, wherein the FORM request comprises card issuing parameters, limit parameters, authorization parameters and batch parameters;
the method comprises the steps that the FORM request also comprises commit No, commit Idex and commit Total, a comprehensive operation platform judges the type of a parameter appointed in the same FORM according to the commit No and carries out splitting operation, a batch of splitting requests and splitting completion instructions after splitting are transmitted to a batch submitting unit, and the same batch of splitting requests have the same batch number;
and after receiving the splitting completion instruction sent by the comprehensive operation platform, the batch submitting unit records the submitted request in a log table of a database DB, analyzes the logs of the same batch in the split logs and calls a maintenance interface. The log table field of the database DB is as shown in the following table.
The distributed parameter cache system provides a unified query interface unit, a unified check interface unit and an interface default implementation unit for the outside, and the interface default implementation unit is used for parameterized services without customized requirements and is used in a default implementation mode without development.
In the core framework, the core interface includes an inquiry interface unit, an inspection interface unit and a maintenance interface unit, and the use and definition of the interface units are as follows:
(1) Query interface unit
Parameter definition:
{
"tableName"// full-size table name defined by common parameter service, also parameter name defined by parameter cache
"condition":(code1=#{code1} AND code2=#{code2}) OR code3=#{code3}
"data":{
"code1":"code1",
"code2":"code2",
"code3":"code3",
}
}
Correspondingly, the definition is as follows:
[ {// parameter validation data
"param1":"value1",
"param2":"value2",
"param3":[{
"param3_1","value3_1",
"param3_2","value3_2"
}]
}]
In the code, a full-size table name in the public parameter service is defined, namely a parameter name defined by parameter cache, and a data inquirer can acquire a parameter result set in a non-differentiated manner through inquiring a parameter API according to a given parameter.
(2) Checking interface unit
Parameter definition:
{
"paramType", "test _01",// parameter type, full table name for common parameter service definition
"checkType": A ",// operation type, A-Add New U-update D-delete
"paramData" {// parameter validation data { /)
"param1":"value1",
"param3":[{"param3_1":"value3_1"}]
}
}
Correspondingly define:
{
"paramType" - "test _01" -/parameter type
"result"// parameter check result
"message": pass,// not pass the error cause
"code"/parameter maintenance result 0-success 1-in-maintenance 2-maintenance error 3-version error not maintenance
}
In the above code, an inspection object, an operation type, and parameter verification data of the inspection interface unit are defined, the inspection object including a parameter type and a full table name of a common parameter service definition, and the operation type including "a-add", "U-update", and "D-delete".
The inspection interface unit executes corresponding 'A-addition', 'U-update' and 'D-deletion' operations according to the comparison inspection result of the inspection object and the parameter verification data, and feeds back the parameter type and the corresponding inspection result. The inspection result comprises a parameter inspection result, reason information and a parameter maintenance result. The parameter checking result comprises "true" or "false", the reason information comprises the reason of "pass" or "fail", and the parameter maintenance result comprises "0-success", "1-maintenance in", "2-maintenance error" or "3-version error not to maintain".
The "true" parameter check result corresponds to cause information of "pass", the "false" parameter check result corresponds to cause information of "fail", and any one of the parameter maintenance results. (3) Maintenance interface unit
Parameter definition:
{
"paramType", "test _01",// parameter type, full table name of common parameter service definition
"operatType" "," A ""// operation type, A-New U-update D-delete
"commit No": 123456",// batch number submitted, if null, only 1 batch
"commit index":1,// index number of the current amount commit
CommitTotal 10,// how many commits are required
"paramData" {// parameter data
"param1":"value1",
"param3":[{"param3_1":"value3_1"}]
}
Unique key value of 'uniKey' { 'key 1' }// parameter unique key value, unique verification of new addition, modification AND deletion as query condition AND connection
}
Correspondingly, the definition is as follows:
{
"paramType", "test _01",/parameter type
"result": true/false ",// parameter maintenance result
Message pass, maintenance failure reason
"code"/parameter maintenance result 0-success 1-in-maintenance 2-maintenance error 3-version error not maintenance
}
In the code, a maintenance object, an operation type, a batch number, a commit index number, commit times, parameter data and a parameter unique key value of the maintenance interface unit are defined, the maintenance object comprises a parameter type and a full-table name defined by a common parameter service, and the operation type comprises 'A-new', 'U-update' and 'D-delete'.
The lot number indicates the lot number submitted when maintenance is performed, and if empty, indicates that there are only 1 lot, e.g., "123456" indicates lot number "123456".
And the maintenance interface unit executes corresponding 'A-addition', 'U-update' and 'D-deletion' operations according to the unique key value of the parameter, and feeds back the type of the parameter and a corresponding check result. The inspection result comprises a parameter maintenance result, reason information and a parameter maintenance result. The parameter maintenance result comprises "true" or "false", the reason information comprises the reason of "pass" or the reason of "maintenance failure", and the parameter maintenance result comprises "0-success", "1-maintenance in", "2-maintenance error" or "3-version error not to maintain".
The "true" parameter check result corresponds to the cause information of "pass", and the "false" parameter check result corresponds to the cause information of "maintenance failure", and any one of the parameter maintenance results.
In summary, the distributed parameter caching system of the present invention does not need to deploy services independently, that is, the embedded type is applied to the service node, and by means of two ways of time-round timing pulling and consumption response pulling of the MQ message of parameter change, the consistency, real-time performance and lightweight level of the parameter caching are ensured efficiently and quickly, various disadvantages caused by network flash and IP switching do not exist, various data structures are supported, the memory space is utilized reasonably, and resource waste does not exist.
Finally, it is noted that the above-mentioned preferred embodiments illustrate rather than limit the invention, and that, although the invention has been described in detail with reference to the above-mentioned preferred embodiments, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention as defined by the appended claims.
Claims (10)
1. A distributed parameter cache system is characterized in that the distributed parameter cache system is used as a middle layer of a public parameter platform, the upper layer is a comprehensive operation platform, and the lower layer is a service module;
the distributed parameter caching system comprises a core framework, an SDK parameter caching module and a file increment processing module; wherein,
the core framework is used for carrying out service initialization on the distributed parameter cache system;
the SDK parameter caching module is used for providing various calling parameters for a service party;
the file increment processing module is used for interfacing with an upper comprehensive operation platform to determine a file format.
2. The distributed parameter caching system of claim 1, wherein the core framework provides 4 interfaces for the integrated operations platform, the interfaces being a query interface, an inspection interface, a maintenance interface, and a split commit interface.
3. The distributed parameter caching system of claim 2, wherein the core framework comprises a maintenance interface unit, a checking interface unit, a query interface unit, an interface default implementation unit, an execution flow unit, a bulk commit unit, a split commit unit, and an analysis log unit, wherein,
the maintenance interface unit, the inspection interface unit and the query interface unit are respectively used for executing the maintenance, inspection and query work of the interfaces;
the interface default realization unit and the execution flow unit are used for realizing the interface function;
the batch submitting unit and the splitting submitting unit are respectively used for realizing batch and splitting submission of the request;
the analysis log unit is used for performing log analysis according to the data docked with the comprehensive operation platform.
4. The distributed parameter caching system of claim 3, wherein the core framework further comprises a service initialization unit, configured to initialize the implementation class of the service when the service is started, bind the service to a corresponding execution flow, and bind the service into a library after the execution of the relevant inspection flow.
5. The distributed parameter caching system according to claim 1, wherein the SDK parameter caching module includes an MQ instruction snooping unit, a timing query unit, and a parameter caching unit, wherein the MQ instruction snooping unit is configured to snoop instructions issued from the core framework, the timing query unit is configured to refresh the cache in real time by means of a time wheel, and the parameter caching unit is configured to cache integrated parameters.
6. The distributed parameter caching system of claim 1, wherein the file delta processing module comprises a file acquisition unit, a file parsing unit, a file comparison unit, and a differencing unit, wherein,
the file acquisition unit is used for receiving files from the comprehensive operation platform according to the file increment request;
the file parsing unit is used for parsing the file received from the integrated operation platform,
the file comparison unit is used for comparing the analyzed file with files in a database DB;
and the differentiation processing unit is used for maintaining the differentiation data with different comparison results again.
7. The distributed parameter caching system of claim 1, wherein the file increment processing module is configured to process common parameter change requests in batches, pull files from the integrated operation platform periodically according to a preset time, realize file format parsing, and provide uniform file increment data comparison correction and database dropping operations.
8. The distributed parameter caching system according to claim 1, wherein the comprehensive operation platform sends the FORM request to a maintenance interface, judges a parameter type specified in the same FORM according to commit no data carried in the FORM request, performs splitting operation, and transmits a batch of split requests and split completion instructions after splitting to a batch submission unit, wherein the same batch of split requests have the same batch number; the FORM request comprises card issuing parameters, limit parameters, authorization parameters and batch parameters.
9. The distributed parameter caching system according to claim 8, wherein the batch submitting unit records the submitted request in a log table of the database DB after receiving the splitting completion instruction sent by the integrated operation platform, parses logs of a same batch in the split logs, and invokes a maintenance interface.
10. The distributed parameter caching system according to claim 1, wherein the core framework is connected to a configuration center, and the configuration center is configured to support business inspection, maintenance inspection, and process configuration of common parameters, and process non-configured common parameters according to default inspection and process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211469823.XA CN115563224A (en) | 2022-11-23 | 2022-11-23 | Distributed parameter caching system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211469823.XA CN115563224A (en) | 2022-11-23 | 2022-11-23 | Distributed parameter caching system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115563224A true CN115563224A (en) | 2023-01-03 |
Family
ID=84770895
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211469823.XA Pending CN115563224A (en) | 2022-11-23 | 2022-11-23 | Distributed parameter caching system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115563224A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117215755A (en) * | 2023-11-07 | 2023-12-12 | 西安博达软件股份有限公司 | Appointment event task scheduling method and system based on time round algorithm |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040006537A1 (en) * | 2002-03-04 | 2004-01-08 | First Data Corporation | Method and system for processing credit card related transactions |
| CN110633320A (en) * | 2018-05-30 | 2019-12-31 | 北京京东尚科信息技术有限公司 | Processing method, system, equipment and storage medium of distributed data service |
| CN114020819A (en) * | 2021-10-26 | 2022-02-08 | 中国银联股份有限公司 | Multi-system parameter synchronization method and device |
| CN114547052A (en) * | 2022-02-14 | 2022-05-27 | 山东浪潮超高清视频产业有限公司 | Method for updating cache of distributed system |
-
2022
- 2022-11-23 CN CN202211469823.XA patent/CN115563224A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040006537A1 (en) * | 2002-03-04 | 2004-01-08 | First Data Corporation | Method and system for processing credit card related transactions |
| CN110633320A (en) * | 2018-05-30 | 2019-12-31 | 北京京东尚科信息技术有限公司 | Processing method, system, equipment and storage medium of distributed data service |
| CN114020819A (en) * | 2021-10-26 | 2022-02-08 | 中国银联股份有限公司 | Multi-system parameter synchronization method and device |
| CN114547052A (en) * | 2022-02-14 | 2022-05-27 | 山东浪潮超高清视频产业有限公司 | Method for updating cache of distributed system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117215755A (en) * | 2023-11-07 | 2023-12-12 | 西安博达软件股份有限公司 | Appointment event task scheduling method and system based on time round algorithm |
| CN117215755B (en) * | 2023-11-07 | 2024-02-06 | 西安博达软件股份有限公司 | Appointment event task scheduling method and system based on time round algorithm |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106888254B (en) | Kubernetes-based container cloud architecture and interaction method among modules thereof | |
| CN101621405B (en) | Distributed type management monitoring system, monitoring method and establishing method thereof | |
| CN102880503B (en) | Data analysis system and data analysis method | |
| US7610582B2 (en) | Managing a computer system with blades | |
| CN107220100A (en) | One kind exploitation O＆M method, device and cloud computing PaaS platform | |
| CN109783151B (en) | Method and device for rule change | |
| CN111639114A (en) | Distributed data fusion management system based on Internet of things platform | |
| CN113301590B (en) | Virtual resource management and control system facing 5G access network | |
| WO2023142924A1 (en) | Electronic map operation and maintenance method, electronic map data use method and service system | |
| CN115563224A (en) | Distributed parameter caching system | |
| CN112311871A (en) | Uniform application development method and system based on micro-service architecture | |
| CN110737710A (en) | Distributed data automatic structured warehousing method and system | |
| CN114448686A (en) | Cross-network communication device and method based on micro-service | |
| CN114003465A (en) | High-reliability low-delay centralized wind control system and method for financial transaction system | |
| CN112579567B (en) | MinIO-based industrial quality inspection file distributed storage method | |
| CN117608845A (en) | Task batch processing method, device, terminal equipment and storage medium | |
| CN116260878A (en) | Service center system based on global service structure server of distributed computing and storage | |
| CN116150263A (en) | Distributed graph calculation engine | |
| CN115373757A (en) | Solving method and device for cluster monitoring data loss in Promethues fragmentation mode | |
| CN112685486B (en) | Data management method and device for database cluster, electronic equipment and storage medium | |
| CN111581256B (en) | Interaction method and system for intelligent measurement terminal application program | |
| CN114816477A (en) | Server upgrading method, device, equipment, medium and program product | |
| CN107102901A (en) | A kind of task processing method and device | |
| CN113011609A (en) | Equipment operation and maintenance system applied to textile printing and dyeing | |
| CN115421748B (en) | Kubernetes container upgrading system and method in multi-cloud environment |
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 |