CN110413543B - API gateway guarantee service high-availability method and system based on fusing and secondary caching - Google Patents
API gateway guarantee service high-availability method and system based on fusing and secondary caching Download PDFInfo
- Publication number
- CN110413543B CN110413543B CN201910520358.XA CN201910520358A CN110413543B CN 110413543 B CN110413543 B CN 110413543B CN 201910520358 A CN201910520358 A CN 201910520358A CN 110413543 B CN110413543 B CN 110413543B
- Authority
- CN
- China
- Prior art keywords
- service
- api gateway
- cache
- api
- fusing
- 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 26
- 230000004044 response Effects 0.000 claims abstract description 44
- 230000002159 abnormal effect Effects 0.000 claims abstract description 13
- 230000015654 memory Effects 0.000 claims abstract description 11
- 238000012544 monitoring process Methods 0.000 claims description 16
- 230000008569 process Effects 0.000 claims description 11
- 238000013500 data storage Methods 0.000 claims description 4
- 238000000926 separation method Methods 0.000 claims description 4
- 238000007664 blowing Methods 0.000 claims 1
- 230000006870 function Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 3
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F12/0893—Caches characterised by their organisation or structure
- G06F12/0897—Caches characterised by their organisation or structure with two or more cache hierarchy levels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a high availability method and a high availability system for an API gateway guarantee service based on fusing and secondary caching. The method comprises the following steps: 1) when receiving a service request sent by a calling party, the API gateway service acquires API configuration information from a memory, determines whether to access the Cache, acquires a response result from a first-level Cache of the Cache if the Cache is started, and sends the service request to a back-end service if the first-level Cache does not have a corresponding response result; 2) the back-end service generates a corresponding response result according to the received service request and puts the response result into a first-level Cache and a second-level Cache of the Cache; and if the number of times of calling the same API gateway service to return the abnormal result reaches the fusing threshold value, entering a fusing flow of the API gateway service, and entering the API gateway service into a fusing starting state. The invention ensures high availability of service and improves user experience.
Description
Technical Field
The invention relates to the field of high availability of API (application programming interface) gateways, fusing, caching and services, in particular to a method and a system for guaranteeing high availability of services for API gateways based on fusing and secondary caching.
Background
With the development of the internet, the network access flow is larger and larger, the requirements on the stability and the availability of the service are higher and higher, and the high availability is taken as an important standard for measuring the performance of the service.
The API gateway is usually used as a unified gateway of the API, and provides functions such as load balancing, service degradation, current limiting, and fusing. Although the existence of these functions can reduce the risk of the downtime of the backend service, and fixed contents can be returned when the backend service is down, these functions cannot guarantee to continuously provide stable and accurate output after the downtime of the backend service, and the user experience is seriously reduced.
The high availability ha (high availability) is designed to reduce the service stop time, thereby achieving the effect of improving the availability of the system and the service.
The API gateway is a service, is the only entrance of the system, encapsulates the internal architecture of the system, provides services for clients uniformly, exists in the micro service architecture with the identity of the micro service gateway, and provides a high-availability solution for the services.
The API gateway provides high available solutions such as load balancing, current limiting, caching, fusing and the like, and specifically comprises the following steps:
1) the load balancing can load the request to each rear-end machine in a balanced manner, and can also dynamically remove the service after the service is down;
2) the gateway directly returns fixed response content through the current limiting function without requesting back-end service when the flow exceeds the preset bearing capacity of the service;
3) the gateway performs Cache on the response result of the request, directly acquires the response result from the Cache after the same request comes, and caches the response content of the back-end service request after the Cache is over;
4) and a fusing function, namely fusing to enter an open state when the request back-end service abnormity reaches a fusing configuration threshold value.
The disadvantages of the prior art solutions include:
1) load balancing reduces the pressure of the back-end service, but the gateway cannot continuously provide available service after all back-end service nodes are down;
2) after the current limiting is effective, all requests return the same content every time, so that the user experience can be reduced;
3) and the cache function is realized, the cache data has a certain validity period, and after the certain validity period expires, all the back-end service nodes are down at the moment, and the gateway cannot normally provide services.
Disclosure of Invention
In order to solve the problems, the invention provides a method and a system for adding a secondary cache to the fusing function of an API gateway, so that the problem that the gateway cannot continuously provide available services is solved by requesting data of the secondary cache after a back-end service node is completely down, high availability of the services is guaranteed through fusing and the secondary cache, and user experience is improved.
The technical scheme of the invention is as follows:
a high availability method of an API gateway guarantee service based on fusing and secondary caching comprises the following steps:
1) when receiving a service request sent by a calling party, the API gateway service acquires API configuration information from a memory; then, whether the Cache is accessed or not is determined according to a Cache opening identifier in the API configuration information, if the Cache is opened, a response result is obtained from a first-level Cache of the Cache, and if the first-level Cache does not have a corresponding response result, the service request is sent to a back-end service; the Cache is used for caching the response result of the service request and is divided into a first-level Cache and a second-level Cache;
2) the back-end service generates a corresponding response result according to the received service request and puts the response result into a first-level Cache and a second-level Cache of the Cache; if the number of times of calling the same API gateway service to return the abnormal result reaches a fusing threshold value, entering a fusing flow of the API gateway service, and entering the API gateway service into a fusing starting state; wherein, the fusing process is as follows: and if the API gateway service receives the service request, directly acquiring a response result from the secondary cache according to the received service request, and if the secondary cache does not have a corresponding response result, returning fusing information.
Further, in the step 2), when the time for the API gateway service to enter the fusing process reaches a set reset time interval, the API gateway service enters a semi-open state; and after the API gateway service enters a semi-open state, directly sending the received first service request to a back-end service, if the back-end service successfully responds to the first service request, quitting the fusing flow of the API gateway service, and simultaneously putting the response into a first-level cache and a second-level cache, otherwise, re-entering the fusing open state of the API gateway service.
Further, data in the Cache is stored in a master-slave synchronization mode; the data updating adopts a read-write separation mode, the main node stores the written and updated data, the slave node obtains the latest changed data from the main node in real time for storage, and the slave node is read when the Cache data is read.
Further, the API configuration information data storage adopts a mode that a single API gateway service stores the full configuration data, that is, a memory of each API gateway service stores one piece of API configuration information.
Further, a plurality of API gateway services are set, and the plurality of API gateway services process all received service requests in parallel.
Further, the system also comprises an API gateway heartbeat monitoring service and an API gateway configuration service; the API gateway heartbeat monitoring service is used for monitoring the state of the back-end service and pushing the state to the API gateway configuration service; and the API gateway configuration service is used for managing API configuration information and pushing the API configuration information to the API gateway service, receiving state information pushed by the API gateway heartbeat monitoring service, deleting the corresponding server from the configuration information when the back-end service is abnormal, and adding the corresponding server into the configuration information when the back-end service is recovered to be normal.
An API gateway guarantee service system based on fusing and secondary caching is characterized by comprising a plurality of back-end services, a plurality of API gateway services and a secondary caching unit Cache; the Cache is used for caching the response result of the service request and is divided into a first-level Cache and a second-level Cache; wherein,
the API gateway service is used for receiving a service request sent by a calling party and acquiring API configuration information from a memory; determining whether to access the Cache according to a Cache opening identifier in the API configuration information, if so, acquiring a response result from a first-level Cache of the Cache, and if not, sending the service request to a back-end service;
the back-end service is used for generating a corresponding response result according to the received service request and putting the response result into a first-level Cache and a second-level Cache of the Cache; if the number of times of calling the same API gateway service to return the abnormal result reaches a fusing threshold value, entering a fusing flow of the API gateway service, and entering the API gateway service into a fusing starting state; wherein, the fusing process is as follows: and if the API gateway service receives the service request, directly acquiring a response result from the secondary cache according to the received service request, and if the secondary cache does not have a corresponding response result, returning fusing information.
The invention has the following advantages and beneficial effects:
the technical method solves the problem of low service support strength caused by the simultaneous downtime of the cache and the service, greatly improves the service availability, ensures the accurate response of the system and optimizes the user experience.
Drawings
Fig. 1 is an overall framework diagram of the present invention.
Fig. 2 is a main flow diagram of the present invention.
FIG. 3 is a flow chart of the fusing method of the present invention.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.
1) Overall composition of
The technical architecture diagram of the invention is shown in figure 1:
the system is additionally provided with Cache on the basis of a calling party, API gateway service, API gateway configuration service, API gateway heartbeat monitoring service and back-end service.
2) Data storage
The API configuration information data storage adopts a mode that a single gateway service stores the full configuration data, namely, the configuration information of the API is stored in the memories of the gateway services A-C, the API configuration data can be stored in full due to the limited data volume of the API configuration information, and the gateway service acquires the API configuration data and directly acquires the API configuration data from the memory of the local machine, so that the reading speed is ensured. The data updating operation adopts a message notification mode, and the gateway service updates the local memory after receiving the message.
The response result data is stored in the Cache, the Cache data adopts a master-slave synchronization mode, only one root node is provided, a plurality of master-slave copy chains can be provided, and the data in the slave library can be approximately in strong consistency. The data updating adopts a common read-write separation mode, the main node stores the written and updated data, the slave node obtains the latest changed data from the main node in real time for storage, and the slave node is read when the Cache data is read, so that the mutual influence between reading and writing is reduced, and the data safety is enhanced.
3) Detailed description of the invention
Main flow: and the network flow sends a service request to the API gateway service, and the API gateway service judges the opening identifier of the first-level cache in the API configuration information. And if the cache is started, acquiring a response result from the first-level cache. And if the first-level cache does not exist, directly requesting the back-end service to obtain a response result, and respectively storing the result in the first-level cache and the second-level cache. And returning an abnormal result if the back-end service is requested to be abnormal. And when the abnormal times of calling the same API reach a fusing threshold value, entering a fusing flow of the API, and ensuring high availability of service through a secondary cache in the fusing flow.
Fusing process: the fusing flow is specific to the APIs, each API has independent fusing, fusing is firstly carried out to enter an open state, if access is requested, the result is directly obtained from the second-level cache, and if the second-level cache does not have the fusing information, the fusing information is returned. And the fusing automatically enters a semi-opening state after reaching the reset time interval. The first request after the semi-open state directly accesses the back-end service, fusing enters the close state if the service response is successful, exiting the fusing process, meanwhile, putting the result into the first-level cache and the second-level cache, and re-entering the fusing open state if the result fails (namely, an abnormal result is returned).
Although specific details of the invention, algorithms and figures are disclosed for illustrative purposes, these are intended to aid in the understanding of the contents of the invention and the implementation in accordance therewith, as will be appreciated by those skilled in the art: various substitutions, changes and modifications are possible without departing from the spirit and scope of the present invention and the appended claims. The invention should not be limited to the preferred embodiments and drawings disclosed herein, but rather should be defined only by the scope of the appended claims.
Claims (10)
1. A high availability method of an API gateway guarantee service based on fusing and secondary caching comprises the following steps:
1) when receiving a service request sent by a calling party, the API gateway service acquires API configuration information from a memory; then, determining whether to start the Cache according to a Cache start identifier in the API configuration information, if the Cache is started, acquiring a response result from a first-level Cache of the Cache, and if the first-level Cache does not have a corresponding response result, sending the service request to a back-end service; the Cache is used for caching the response result of the service request and is divided into a first-level Cache and a second-level Cache;
2) the back-end service generates a corresponding response result according to the received service request and puts the response result into a first-level Cache and a second-level Cache of the Cache; if the number of times of calling the same API gateway service to return the abnormal result reaches a fusing threshold value, entering a fusing flow of the API gateway service, and entering the API gateway service into a fusing starting state; wherein, the fusing process is as follows: and if the API gateway service receives the service request, directly acquiring a response result from the secondary cache according to the received service request, and if the secondary cache does not have a corresponding response result, returning fusing information.
2. The method of claim 1, wherein in step 2), when the time for the API gateway service to enter the fusing process reaches a set reset time interval, the API gateway service enters a semi-open state; and after the API gateway service enters a semi-open state, directly sending the received first service request to a back-end service, if the back-end service successfully responds to the first service request, quitting the fusing flow of the API gateway service, and simultaneously putting the response into a first-level cache and a second-level cache, otherwise, re-entering the fusing open state of the API gateway service.
3. The method of claim 2, wherein the data in the Cache is stored in a master-slave synchronization manner; the data updating adopts a read-write separation mode, the main node stores the written and updated data, the slave node obtains the latest changed data from the main node in real time for storage, and the slave node is read when the Cache data is read.
4. The method of claim 1, wherein the API configuration information data storage is in a manner that a single API gateway service stores the full configuration data, i.e., a memory of each API gateway service stores a copy of the API configuration information.
5. The method of claim 1, wherein a plurality of API gateway services are provided, the plurality of API gateway services processing all received service requests in parallel.
6. The method of claim 1, further comprising an API gateway heartbeat monitoring service and an API gateway configuration service; the API gateway heartbeat monitoring service is used for monitoring the state of the back-end service and pushing the state to the API gateway configuration service; and the API gateway configuration service is used for managing API configuration information, pushing the API configuration information to the API gateway service, receiving state information pushed by the API gateway heartbeat monitoring service, deleting the corresponding server from the configuration information when the back-end service is abnormal, and adding the corresponding server into the configuration information when the back-end service is recovered to be normal.
7. An API gateway guarantee service system based on fusing and secondary caching is characterized by comprising a plurality of back-end services, a plurality of API gateway services and a secondary caching unit Cache; the Cache is used for caching the response result of the service request and is divided into a first-level Cache and a second-level Cache; wherein,
the API gateway service is used for receiving a service request sent by a calling party and acquiring API configuration information from a memory; determining whether to start the Cache according to a Cache start identifier in the API configuration information, if the Cache is started, acquiring a response result from a first-level Cache of the Cache, and if the first-level Cache does not have a corresponding response result, sending the service request to a back-end service;
the back-end service is used for generating a corresponding response result according to the received service request and putting the response result into a first-level Cache and a second-level Cache of the Cache; if the number of times of calling the same API gateway service to return the abnormal result reaches a fusing threshold value, entering a fusing flow of the API gateway service, and entering the API gateway service into a fusing starting state; wherein, the fusing process is as follows: and if the API gateway service receives the service request, directly acquiring a response result from the secondary cache according to the received service request, and if the secondary cache does not have a corresponding response result, returning fusing information.
8. The system of claim 7, wherein the API gateway service enters a semi-open state when the time for the API gateway service to enter the blowing process reaches a set reset time interval; and after the API gateway service enters a semi-open state, directly sending the received first service request to a back-end service, if the back-end service successfully responds to the first service request, quitting the fusing flow of the API gateway service, and simultaneously putting the response into a first-level cache and a second-level cache, otherwise, re-entering the fusing open state of the API gateway service.
9. The system of claim 7, further comprising an API gateway heartbeat monitoring service and an API gateway configuration service; the API gateway heartbeat monitoring service is used for monitoring the state of the back-end service and pushing the state to the API gateway configuration service; and the API gateway configuration service is used for managing API configuration information, pushing the API configuration information to the API gateway service, receiving state information pushed by the API gateway heartbeat monitoring service, deleting the corresponding server from the configuration information when the back-end service is abnormal, and adding the corresponding server into the configuration information when the back-end service is recovered to be normal.
10. The system of claim 7, wherein data in the Cache is stored in a master-slave synchronization manner; the data updating adopts a read-write separation mode, the main node stores the written and updated data, the slave node obtains the latest changed data from the main node in real time for storage, and the slave node is read when the Cache data is read.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910520358.XA CN110413543B (en) | 2019-06-17 | 2019-06-17 | API gateway guarantee service high-availability method and system based on fusing and secondary caching |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910520358.XA CN110413543B (en) | 2019-06-17 | 2019-06-17 | API gateway guarantee service high-availability method and system based on fusing and secondary caching |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110413543A CN110413543A (en) | 2019-11-05 |
| CN110413543B true CN110413543B (en) | 2021-04-27 |
Family
ID=68359153
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910520358.XA Active CN110413543B (en) | 2019-06-17 | 2019-06-17 | API gateway guarantee service high-availability method and system based on fusing and secondary caching |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110413543B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111078453B (en) * | 2019-12-17 | 2024-03-29 | 深圳前海环融联易信息科技服务有限公司 | Method, device, computer equipment and storage medium for automatically fusing and recovering micro-service |
| CN111580945A (en) * | 2020-04-21 | 2020-08-25 | 智业互联（厦门）健康科技有限公司 | Micro-service task coordination scheduling method and system |
| CN112449017B (en) * | 2020-11-25 | 2023-08-18 | 深圳市欢太科技有限公司 | Service end and control method thereof |
| CN112468583B (en) * | 2020-11-26 | 2023-09-15 | 福建天泉教育科技有限公司 | Information processing method and terminal of API gateway |
| CN112217684A (en) * | 2020-12-03 | 2021-01-12 | 长沙树根互联技术有限公司 | API gateway monitoring method, device and system |
| CN113595925B (en) * | 2021-07-06 | 2024-01-30 | 中企云链（北京）金融信息服务有限公司 | Method for realizing dynamic current limiting of intelligent gateway |
| CN113722363B (en) * | 2021-08-19 | 2023-09-12 | 成都民航西南凯亚有限责任公司 | Cache public assembly and implementation, installation and operation methods thereof |
| CN114785637B (en) * | 2022-03-15 | 2024-08-09 | 浪潮云信息技术股份公司 | Implementation method and system for API gateway cache response data |
| CN115065588B (en) * | 2022-05-31 | 2024-04-05 | 浪潮云信息技术股份公司 | API fusing degradation realization method and system based on back-end error code |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109189652A (en) * | 2018-06-26 | 2019-01-11 | 中国科学院信息工程研究所 | A kind of acquisition method and system of close network terminal behavior data |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5812775A (en) * | 1995-07-12 | 1998-09-22 | 3Com Corporation | Method and apparatus for internetworking buffer management |
| JP2002279794A (en) * | 2001-03-21 | 2002-09-27 | Mitsubishi Electric Corp | Semiconductor memory |
| CN106776099B (en) * | 2017-01-11 | 2020-01-03 | 北京皮尔布莱尼软件有限公司 | Service fusing isolation system and method |
| CN108933832A (en) * | 2018-07-17 | 2018-12-04 | 河北中科恒运软件科技股份有限公司 | A method of realizing that full stage grid is shared |
| CN109672612A (en) * | 2018-12-13 | 2019-04-23 | 中国电子科技集团公司电子科学研究院 | API gateway system |
-
2019
- 2019-06-17 CN CN201910520358.XA patent/CN110413543B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109189652A (en) * | 2018-06-26 | 2019-01-11 | 中国科学院信息工程研究所 | A kind of acquisition method and system of close network terminal behavior data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110413543A (en) | 2019-11-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110413543B (en) | API gateway guarantee service high-availability method and system based on fusing and secondary caching | |
| CN111800458B (en) | Dynamic load balancing method and system for Kubernetes container cloud platform | |
| CN112260876B (en) | Dynamic gateway route configuration method, platform, computer equipment and storage medium | |
| CN108712457B (en) | Method and device for adjusting dynamic load of back-end server based on Nginx reverse proxy | |
| US9450912B2 (en) | Method and device for accessing application server | |
| CN112578997B (en) | Data migration method, system and related equipment | |
| CN112134721B (en) | API gateway degradation method and terminal | |
| CN106790629A (en) | Data synchronization unit and its realize the method for data syn-chronization, client access system | |
| CN113010818A (en) | Access current limiting method and device, electronic equipment and storage medium | |
| US20130198313A1 (en) | Using entity tags (etags) in a hierarchical http proxy cache to reduce network traffic | |
| WO2015090243A1 (en) | Ip management method, client and server | |
| CN113010549A (en) | Data processing method based on remote multi-active system, related equipment and storage medium | |
| US20230359628A1 (en) | Blockchain-based data processing method and apparatus, device, and storage medium | |
| TW201724001A (en) | System and method for acquiring, processing and updating global information | |
| TWI716822B (en) | Method and device for correcting transaction causality, and electronic equipment | |
| WO2022127319A1 (en) | Data refreshing method and apparatus, and electronic device and computer-readable storage medium | |
| WO2024104073A1 (en) | Metadata access method and device, and storage medium | |
| US11288237B2 (en) | Distributed file system with thin arbiter node | |
| US9344363B2 (en) | Information processing system, relay device, information processing device, and information processing method | |
| CN103023704A (en) | Method and system for accessing virtual network service equipment | |
| CN115470303B (en) | Database access method, device, system, equipment and readable storage medium | |
| CN115934338A (en) | Inter-process communication method and device | |
| CN116028530A (en) | Object resource reading method and device, electronic equipment and readable storage medium | |
| CN105357222B (en) | A kind of distribution Session management middleware | |
| CN115695587A (en) | Service data processing system, method, device and storage medium |
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 |