WO2017092356A1 - 用于提供服务数据的服务器、方法及系统 - Google Patents

用于提供服务数据的服务器、方法及系统 Download PDF

Info

Publication number
WO2017092356A1
WO2017092356A1 PCT/CN2016/089515 CN2016089515W WO2017092356A1 WO 2017092356 A1 WO2017092356 A1 WO 2017092356A1 CN 2016089515 W CN2016089515 W CN 2016089515W WO 2017092356 A1 WO2017092356 A1 WO 2017092356A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
cache
client
found
read request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2016/089515
Other languages
English (en)
French (fr)
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.)
Le Holdings Beijing Co Ltd
LeTV Information Technology Beijing Co Ltd
Original Assignee
Le Holdings Beijing Co Ltd
LeTV Information Technology Beijing 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 Le Holdings Beijing Co Ltd, LeTV Information Technology Beijing Co Ltd filed Critical Le Holdings Beijing Co Ltd
Priority to US15/236,519 priority Critical patent/US20170155741A1/en
Publication of WO2017092356A1 publication Critical patent/WO2017092356A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5682—Policies or rules for updating, deleting or replacing the stored data

Definitions

  • the present patent application relates to the field of computers, and in particular to a server, method and system for providing service data.
  • the server when receiving a data service request from a client, the server queries the corresponding data from the database stored on the disk, and sends the query data to the client to respond to the data service request. .
  • the response time of the server to the data service request from the client is too long, and it is difficult for the user who operates the client to have Good service experience.
  • an embodiment of the present invention provides a server for providing service data, the server comprising: receiving means for receiving a data read request from a client; and processing means for buffering from the local machine Find the data requested by the data read request, and execute One of the following: in the case where the data is found, the data is sent from the local cache to the client; if the data is not found, the data is searched from the cluster cache and the data is sent To the client.
  • the processing device is further configured to update the data found from the cluster cache to the local cache without finding the data from the local cache.
  • the data read request is an application update request.
  • the processing device is further configured to update the latest version of each application in the cluster cache to the local cache in a case that the data read request is an application update request.
  • an embodiment of the present invention further provides a data service system, including: a client; and the foregoing server.
  • an embodiment of the present invention further provides a method for providing service data, the method comprising: receiving a data read request from a client; and searching for data requested by the data read request from a local cache And performing one of: sending the data from the local cache to the client if the data is found; if the data is not found, looking for the data from the cluster cache and Data is sent to the client.
  • the data found from the cluster cache is updated to the local cache without the data being found from the local cache.
  • the data read request is an application update request.
  • the latest version of each application in the cluster cache is updated to the local cache.
  • a data update mechanism between a cluster cache of a server and a local cache is provided.
  • the server may first search for the data requested by the data read request in the local cache, and if so, may directly send the data to the client; if not, the slave cache may be Search for the data requested by the data read request and send the data to the client.
  • the data cache speed of the local cache (the response time is generally 1ms) is much higher than the cluster cache (the response time is generally 10ms), so it can greatly improve the server's response speed to data read requests.
  • the data update mechanism between the cluster cache and the local cache provided by an embodiment of the present invention can ensure that the data requested by the data read request from most clients can be found from the local cache, reducing the need The probability of sending data requested by a data read request to the client from the cluster cache, providing the server with a response to most data read requests.
  • FIG. 1 is a schematic structural diagram of a data service system according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for providing service data according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for providing service data according to an embodiment of the present invention, where a data read request is an application update request.
  • “Local Cache” refers to the server-specific cache itself, which typically has a response speed of 1ms, but the capacity is fixed.
  • a typical representation of the "local cache” is EhCache, which is a pure Java in-process caching framework with fast, lean features.
  • Cluster Cache refers to the case where there are multiple service nodes forming a server cluster, each service node will contribute a part of the cache, so that the server cluster forms a cluster cache, which is contributed by each service node. Cache composition.
  • the response speed of the cluster cache is slower than that of the local cache, which is generally 10 ms, but its capacity can be expanded as needed. For example, by adding more service nodes or serving nodes to contribute a larger capacity cache. The expansion of the cluster cache.
  • FIG. 1 is a schematic structural diagram of a data service system according to an embodiment of the present invention.
  • an embodiment of the present invention provides a data service system including a client 100 and a server 200 for providing service data, the server 200 including a receiving device 210, a processing device 220, and a local cache. 230, cluster cache 240 and database 250.
  • the database 250 stores all service content data (including various types of data, such as user collections, user reviews, application versions, application packages, application other information, etc.) that can be provided by the data service system, which can be timed ( The service content data is updated to the cluster cache 240, for example, every 5 minutes.
  • the local cache 230 has an expiration policy, and the data therein automatically expires after a predetermined time (e.g., 5 minutes).
  • the receiving device 210 is configured to receive a data read request from the client 100.
  • the processing device 220 is configured to look up data requested by the data read request from the local cache 230 and perform one of: sending the data from the local cache 230 to the local cache 230 if the data is found The client 100; from the cluster cache 240 if the data is not found The data is looked up and sent to the client 100. Thereby, by first looking for data in the local cache 230 and transmitting the data to the client 100 in the case of finding the data, the response speed of the server 200 to the data read request can be increased.
  • the server 200 included in the above description includes a cluster cache mainly considering that a partial cache of the cluster cache is contributed by the server 200, and the cluster cache can actually serve as a separate component other than the server 200. This is for the purpose of simplifying the description and directly including the cluster cache in the server 200 for introduction.
  • the processing device 220 is further configured to update the data found from the cluster cache 240 to the local cache 230 without the data being found from the local cache 230.
  • the probability of finding data requested by the data read request from the local cache 230 can be increased, because in most cases, the server 200 may receive the same request from multiple clients 100 at the same time. For example, during the Christmas period, users may focus on accessing a Christmas-themed web page, in which case the user may need to retrieve data from the cluster cache for the first visited user.
  • the response speed of 200 is general, but for subsequent user access, it is possible to find the data to be accessed from the local cache 230, thereby improving the response speed to the subsequent user access.
  • the data read request may be an application update request.
  • the processing of the application update request is basically the same as the above-mentioned processing for the general data read request, that is, the latest version of the application for which the application update request is directed is first searched from the local cache 230, and the latest version of the application is found. In the case of the version, the latest version of the application is sent to the client 100; if the latest version of the application is not found from the local cache 230, the latest version of the application is looked up from the cluster cache 240 and will be The latest version of the application is sent to the client 100.
  • the processing device also updates the latest version of each application in the cluster cache 240 to the local cache 230, that is, whether the latest version of the application is found from the local cache 230, The latest version of each application in the cluster cache 240 is updated to the native cache 230.
  • the processing device may The latest version of the application for which the application update request is directed is found directly from the local cache 230, and the latest version is sent to the client 100, improving the response speed of the application update request to other clients 100.
  • FIG. 2 is a flowchart of a method for providing service data according to an embodiment of the present invention. Accordingly, as shown in FIG. 2, an embodiment of the present invention further provides a method for providing service data, the method comprising: receiving a data read request from a client 100; and finding the same from the local cache 230. The data reads the requested data and performs one of: sending the data from the local cache 230 to the client 100 if the data is found; if the data is not found, The data is looked up from the cluster cache 240 and sent to the client 100. Wherein, the data found from the cluster cache 240 is updated to the local cache 230 without the data being found from the local cache 230.
  • the data read request may be an application update request.
  • FIG. 3 is a flowchart of a method for providing service data according to an embodiment of the present invention, where a data read request is an application update request. As shown in FIG. 3, where the data read request is an application update request, the method further includes updating the latest version of each application in the cluster cache 240 to the native cache 230.
  • the data read request by first searching for the data requested by the data read request from the local cache 230, if the data can be found, the data can be directly sent to the client 100, due to the local The response of the cache 230 is faster, thereby increasing the response speed of the server 200 to the data read request. Even if the data cannot be found from the local cache 230, the data can still be found from the cluster cache 240 and sent to the client 100. At the same time, updating the data to the local cache 230 ensures that data requested by the same data read request from other clients 100 can be found from the local cache 230, improving the server 200 to other clients. 100 response speed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Multimedia (AREA)
  • Software Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Computational Linguistics (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本发明一个实施例涉及计算机领域，公开了一种用于提供服务数据的服务器、方法及系统，其中该服务器包括：接收装置，用于接收来自客户端的数据读取请求；以及处理装置，用于从本机缓存内寻找该数据读取请求所请求的数据，并执行以下一者：在找到该数据的情况下，从所述本机缓存将该数据发送至所述客户端；在未找到该数据的情况下，从集群缓存寻找该数据，并将该数据发送至所述客户端。由于本机缓存的数据存取速度要远高于集群缓存因此可极大地提升服务器对数据读取请求的响应速度。

Description

用于提供服务数据的服务器、方法及系统
本申请基于申请号为201510864355.X、申请日为2015/12/1的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本专利申请涉及计算机领域，具体地，涉及一种用于提供服务数据的服务器、方法及系统。
背景技术
目前，服务器在接收到来自客户的数据服务请求时，多从其磁盘上所存储的数据库内查询相应的数据，并将查询到数据发送给所述客户端，以对所述数据服务请求进行响应。然而，由于通信环境(诸如，网络带宽、信号接收强度、信号干扰等)以及服务器处理速度的限制，导致服务器对来自客户端的数据服务请求的响应时间过长，难以使得操作所述客户端的用户具有良好的服务体验。
如何提高服务器对数据服务请求的响应速度一致是本领域所致力于解决的一技术难题。
发明内容
本发明部分实施例的目的是提供一种用于服务器的全新数据处理方式，可助于减小该服务器对数据服务请求的响应时间。
为了实现上述目的，本发明一个实施例提供了一种用于提供服务数据的服务器，该服务器包括：接收装置，用于接收来自客户端的数据读取请求；以及处理装置，用于从本机缓存内寻找该数据读取请求所请求的数据，并执 行以下一者：在找到该数据的情况下，从所述本机缓存将该数据发送至所述客户端；在未找到该数据的情况下，从集群缓存寻找该数据，并将该数据发送至所述客户端。
其中，所述处理装置还用于在未从所述本机缓存找到所述数据的情况下，将从所述集群缓存找到的所述数据更新至所述本机缓存。
其中，所述数据读取请求为应用更新请求。
其中，在所述数据读取请求为应用更新请求的情况下，所述处理装置还用于将所述集群缓存内每个应用的最新版本更新至所述本机缓存。
相应地，本发明一个实施例还提供了一种数据服务系统，该系统包括：客户端；以及上述服务器。
相应地，本发明一个实施例还提供了一种用于提供服务数据的方法，该方法包括：接收来自客户端的数据读取请求；以及从本机缓存内寻找该数据读取请求所请求的数据，并执行以下一者：在找到该数据的情况下，从所述本机缓存将该数据发送至所述客户端；在未找到该数据的情况下，从集群缓存寻找该数据，并将该数据发送至所述客户端。
其中，在未从所述本机缓存找到所述数据的情况下，将从所述集群缓存找到的所述数据更新至所述本机缓存。
其中，所述数据读取请求为应用更新请求。
其中，在所述数据读取请求为应用更新请求的情况下，将所述集群缓存内每个应用的最新版本更新至所述本机缓存。
通过上述技术方案，提供了一种服务器的集群缓存与本机缓存之间的数据更新机制。针对每一数据读取请求，服务器可首先在本机缓存搜索是否存在该数据读取请求所请求的数据，如果存在，可直接将该数据发送给客户端；如果不存在，可从集群缓存内搜索该数据读取请求所请求的数据，并将该数据发送给客户端。一般来说，本机缓存的数据存取速度(其响应时间一般为 1ms)要远高于集群缓存(其响应时间一般为10ms)，因此可极大地提升服务器对数据读取请求的响应速度。另外，通过本发明一个实施例所提供的集群缓存与本机缓存之间的数据更新机制，可保证来自大部分客户端的数据读取请求所请求的数据均可从本机缓存内找到，减少需从集群缓存将数据读取请求所请求的数据发送至客户端的几率，提供服务器对大部分数据读取请求的响应速度。
本发明部分实施例的其它特征和优点将在随后的具体实施方式部分予以详细说明。
附图说明
附图是用来提供对本发明部分实施例的进一步理解，并且构成说明书的一部分，与下面的具体实施方式一起用于解释本发明，但并不构成对本发明的限制。在附图中：
图1为本发明一个实施例提供的数据服务系统的结构示意图；
图2为本发明一个实施例提供的提供服务数据的方法的流程图；以及
图3为本发明一个实施例提供的提供服务数据的方法在数据读取请求为应用更新请求的情况下的流程图。
附图标记说明
100  客户端    200  服务器
210  接收装置  220  处理装置
230  本机缓存  240  集群缓存
250  数据库
具体实施方式
以下结合附图对本发明部分实施例的具体实施方式进行详细说明。应当理解的是，此处所描述的具体实施方式仅用于说明和解释本发明，并不用于限制本发明。
在对本发明部分实施例的具体实施方式进行介绍之前，先解释一下以下说明中所涉及的两个概念：“本地缓存”以及“集群缓存”。“本地缓存”指服务器专用自身的缓存，其响应速度一般为1ms，但容量是固定的。该“本地缓存”的一个典型代表为EhCache，其为一个纯Java的进程内缓存框架，具有快速、精干等特点。“集群缓存”指的是在存在多个服务节点构成服务器集群的情况下，每一服务节点会贡献一部分缓存，这样服务器集群就形成了一个集群缓存，该集群缓存由每一服务节点所贡献的缓存构成。该集群缓存的响应速度较所述本地缓存为慢，一般为10ms，但其容量是可以根据需要进行扩容的，例如可通过加入更多的服务节点或者是服务节点贡献更大容量的缓存来实现该集群缓存的扩容。
图1为本发明一个实施例提供的数据服务系统的结构示意图。如图1所示，本发明一个实施例提供了一种数据服务系统，该系统包含客户端100以及用于提供服务数据的服务器200，该服务器200包括接收装置210、处理装置220、本机缓存230、集群缓存240以及数据库250。其中数据库250存储了有关该数据服务系统所能提供的所有服务内容数据(包含各种类型的数据，诸如用户收藏、用户评论、应用版本、应用礼包、应用其他信息等等)，其可定时(例如每隔5分钟)将该服务内容数据更新至所述集群缓存240。所述本机缓存230具有一失效策略，其内的数据在预定时间(例如，5分钟)之后会自动失效。所述接收装置210用于接收来自客户端100的数据读取请求。所述处理装置220用于从本机缓存230内寻找该数据读取请求所请求的数据，并执行以下一者：在找到该数据的情况下，从所述本机缓存230将该数据发送至所述客户端100；在未找到该数据的情况下，从集群缓存240 寻找该数据，并将该数据发送至所述客户端100。藉此，通过首先在本机缓存230内寻找数据，并在寻找到数据的情况下将该数据发送至客户端100，从而可提高服务器200对数据读取请求的响应速度。
需要说明的是，上述介绍中所出现的服务器200包含集群缓存主要是考虑到集群缓存的部分缓存是由该服务器200贡献的，该集群缓存实际上可作为服务器200之外的一独立组件，在此只是出于简化描述的目的而直接将该集群缓存包含在了服务器200内进行介绍。
其中，所述处理装置220还用于在未从所述本机缓存230找到所述数据的情况下，将从所述集群缓存240找到的所述数据更新至所述本机缓存230。藉此，可增大从本机缓存230内找到数据读取请求所请求的数据的几率，因为在大多数情况下，服务器200可能会在同一时间收到来自多个客户端100相同的请求。例如在圣诞节时期，用户可能会集中对某一以圣诞节为主题的网页进行访问，而在此情况下，虽然对于第一个访问的用户而言，其可能需要从集群缓存获取数据，服务器200的响应速度一般，但对于后续的用户访问而言，均可能从本机缓存230找到所要访问的数据，从而提高了对该后续用户访问的响应速度。
其中，所述数据读取请求可为应用更新请求。对于该应用更新请求的处理，与上述介绍的针对一般数据读取请求的处理基本一致，即首先从本机缓存230内寻找应用更新请求所针对的应用的最新版本，并在找到该应用的最新版本的情况下，将该应用的最新版本发送至客户端100；在没有从本机缓存230内找到该应用的最新版本的情况下，从集群缓存240内寻找该应用的最新版本，并将该应用的最新版本发送至客户端100。所不同的使，所述处理装置还会将所述集群缓存240内每个应用的最新版本更新至所述本机缓存230，即无论是否从本机缓存230内找到该应用的最新版本，均会将所述集群缓存240内每个应用的最新版本更新至所述本机缓存230。这样主要 是考虑了每一客户端100可能所需更新的应用是不同的，而将每一应用的最新版本更新至本机缓存230之后，对于其他客户端100的后续应用更新请求而言，处理装置可直接从本机缓存230找到该应用更新请求所针对的应用的最新版本，并将该最新版本发送给客户端100，提高了对其他客户端100的应用更新请求的响应速度。
图2为本发明一个实施例提供的提供服务数据的方法的流程图。相应地，如图2所示，本发明一个实施例还提供一种用于提供服务数据的方法，该方法包括：接收来自客户端100的数据读取请求；以及从本机缓存230内寻找该数据读取请求所请求的数据，并执行以下一者：在找到该数据的情况下，从所述本机缓存230将该数据发送至所述客户端100；在未找到该数据的情况下，从集群缓存240寻找该数据，并将该数据发送至所述客户端100。其中，在未从所述本机缓存230找到所述数据的情况下，将从所述集群缓存240找到的所述数据更新至所述本机缓存230。
其中，所述数据读取请求可为应用更新请求。图3为本发明一个实施例提供的提供服务数据的方法在数据读取请求为应用更新请求的情况下的流程图。如图3所示，在所述数据读取请求为应用更新请求的情况下，所述方法还包括将所述集群缓存240内每个应用的最新版本更新至所述本机缓存230。
通过本发明一个实施例的方案，通过首先从本机缓存230寻找数据读取请求所请求的数据，在能够寻找到该数据的情况下，可直接将该数据发送至客户端100，由于本机缓存230的响应速度较快，藉此可提高服务器200对数据读取请求的响应速度。即便是无法从本机缓存230找到所述数据，依旧可从集群缓存240内找到所述数据并将该数据发送给客户端100。而同时将该数据更新本机缓存230，可保证来自其他客户端100的相同数据读取请求所请求的数据可从本机缓存230内找到，提高服务器200对其他客户端 100的响应速度。本实施例通过对集群缓存240与本机缓存230之间的数据进行灵活调配，可保证大部分数据均可直接从本机缓存230读取，提高服务器200对于客户端100的数据读取请求的响应速度。
以上结合附图详细描述了本发明部分实施例的优选实施方式，但是，本发明并不限于上述实施方式中的具体细节，在本发明的技术构思范围内，可以对本发明的技术方案进行多种简单变型，这些简单变型均属于本发明的保护范围。
另外需要说明的是，在上述具体实施方式中所描述的各个具体技术特征，在不矛盾的情况下，可以通过任何合适的方式进行组合。为了避免不必要的重复，本发明对各种可能的组合方式不再另行说明。
此外，本发明的各种不同的实施方式之间也可以进行任意组合，只要其不违背本发明的思想，其同样应当视为本发明所公开的内容。

Claims (9)

  1. 一种用于提供服务数据的服务器，包括：
    接收装置，用于接收来自客户端的数据读取请求；以及
    处理装置，用于从本机缓存内寻找该数据读取请求所请求的数据，并执行以下一者：
    在找到该数据的情况下，从所述本机缓存将该数据发送至所述客户端；
    在未找到该数据的情况下，从集群缓存寻找该数据，并将该数据发送至所述客户端。
  2. 根据权利要求1所述的服务器，其中，所述处理装置还用于在未从所述本机缓存找到所述数据的情况下，将从所述集群缓存找到的所述数据更新至所述本机缓存。
  3. 根据权利要求1或2所述的服务器，其中，所述数据读取请求为应用更新请求。
  4. 根据权利要求3所述的服务器，其中，在所述数据读取请求为应用更新请求的情况下，所述处理装置还用于将所述集群缓存内每个应用的最新版本更新至所述本机缓存。
  5. 一种数据服务系统，包括：
    客户端；以及
    根据权利要求1-4中任一项权利要求所述的服务器。
  6. 一种用于提供服务数据的方法，包括：
    接收来自客户端的数据读取请求；以及
    从本机缓存内寻找该数据读取请求所请求的数据，并执行以下一者：
    在找到该数据的情况下，从所述本机缓存将该数据发送至所述客户端；
    在未找到该数据的情况下，从集群缓存寻找该数据，并将该数据发送至所述客户端。
  7. 根据权利要求6所述的方法，其中，在未从所述本机缓存找到所述数据的情况下，将从所述集群缓存找到的所述数据更新至所述本机缓存。
  8. 根据权利要求6或7所述的方法，其中，所述数据读取请求为应用更新请求。
  9. 根据权利要求8所述的方法，其中，在所述数据读取请求为应用更新请求的情况下，将所述集群缓存内每个应用的最新版本更新至所述本机缓存。
PCT/CN2016/089515 2015-12-01 2016-07-10 用于提供服务数据的服务器、方法及系统 Ceased WO2017092356A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/236,519 US20170155741A1 (en) 2015-12-01 2016-08-15 Server, method, and system for providing service data

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510864355.XA CN105897832A (zh) 2015-12-01 2015-12-01 用于提供服务数据的服务器、方法及系统
CN201510864355X 2015-12-01

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/236,519 Continuation US20170155741A1 (en) 2015-12-01 2016-08-15 Server, method, and system for providing service data

Publications (1)

Publication Number Publication Date
WO2017092356A1 true WO2017092356A1 (zh) 2017-06-08

Family

ID=57002024

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/089515 Ceased WO2017092356A1 (zh) 2015-12-01 2016-07-10 用于提供服务数据的服务器、方法及系统

Country Status (2)

Country Link
CN (1) CN105897832A (zh)
WO (1) WO2017092356A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110471868A (zh) * 2019-08-21 2019-11-19 携程旅游信息技术（上海）有限公司 提高soa接口响应速度的方法、系统、设备及介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109995855B (zh) * 2019-03-20 2021-12-10 北京奇艺世纪科技有限公司 一种数据获取方法、装置及终端

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101090401A (zh) * 2007-05-25 2007-12-19 金蝶软件（中国）有限公司 一种群集环境下的数据缓存方法及系统
CN101610211A (zh) * 2009-07-15 2009-12-23 浪潮电子信息产业股份有限公司 一种实现加权轮询的高速缓存负载均衡方法
CN101764848A (zh) * 2010-01-12 2010-06-30 浪潮(北京)电子信息产业有限公司 传输网络文件的方法和装置
CN102143212A (zh) * 2010-12-31 2011-08-03 华为技术有限公司 一种内容分发网络中缓存共享的方法及装置
US20120110113A1 (en) * 2009-07-02 2012-05-03 Aim To G Co., Ltd. Cooperative Caching Method and Contents Providing Method Using Request Apportioning Device
CN105635196A (zh) * 2014-10-27 2016-06-01 中国电信股份有限公司 一种获取文件数据的方法、系统和应用服务器

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1770954A1 (en) * 2005-10-03 2007-04-04 Amadeus S.A.S. System and method to maintain coherence of cache contents in a multi-tier software system aimed at interfacing large databases
CN102694828B (zh) * 2011-03-23 2016-03-30 中兴通讯股份有限公司 一种分布式缓存系统数据存取的方法及装置
CN103825922B (zh) * 2012-11-19 2018-02-06 华为技术有限公司 一种数据更新方法及web服务器

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101090401A (zh) * 2007-05-25 2007-12-19 金蝶软件（中国）有限公司 一种群集环境下的数据缓存方法及系统
US20120110113A1 (en) * 2009-07-02 2012-05-03 Aim To G Co., Ltd. Cooperative Caching Method and Contents Providing Method Using Request Apportioning Device
CN101610211A (zh) * 2009-07-15 2009-12-23 浪潮电子信息产业股份有限公司 一种实现加权轮询的高速缓存负载均衡方法
CN101764848A (zh) * 2010-01-12 2010-06-30 浪潮(北京)电子信息产业有限公司 传输网络文件的方法和装置
CN102143212A (zh) * 2010-12-31 2011-08-03 华为技术有限公司 一种内容分发网络中缓存共享的方法及装置
CN105635196A (zh) * 2014-10-27 2016-06-01 中国电信股份有限公司 一种获取文件数据的方法、系统和应用服务器

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110471868A (zh) * 2019-08-21 2019-11-19 携程旅游信息技术（上海）有限公司 提高soa接口响应速度的方法、系统、设备及介质

Also Published As

Publication number Publication date
CN105897832A (zh) 2016-08-24

Similar Documents

Publication Publication Date Title
US20220321927A1 (en) Providing access to managed content
AU2015401229B2 (en) Website access method, apparatus, and website system
CN106603713B (zh) 会话管理方法和系统
CN103957239B (zh) Dns缓存信息处理方法、设备及系统
JP6588477B2 (ja) リモート情報クエリの方法及びサーバ
WO2018184491A1 (zh) 资源获取方法、装置及系统
WO2019165665A1 (zh) 一种域名解析方法、服务器及系统
EP1376989A2 (en) Method and apparatus for determination of device capabilities on a network
EP3557841A1 (en) Dns attack defense method, apparatus and system
KR20160030381A (ko) 웹 페이지 액세스 방법, 장치, 라우터, 프로그램 및 기록매체
WO2017092351A1 (zh) 缓存数据的更新方法及装置
US20160323238A1 (en) Ip management method, client and server
CN115964389B (zh) 基于区块链的数据处理方法、装置、设备及可读存储介质
CN106897344A (zh) 分布式数据库的数据操作请求处理方法及装置
Gessert et al. Towards a Scalable and Unified REST API for Cloud Data Stores.
US8713088B2 (en) Identifying users of remote sessions
US10574745B2 (en) Syncing with a local paired device to obtain data from a remote server using point-to-point communication
US11442960B2 (en) Edge key value store for a distributed platform
WO2017092356A1 (zh) 用于提供服务数据的服务器、方法及系统
CN103957252B (zh) 云储存系统的日志获取方法及其系统
CN115658171A (zh) 一种轻量级解决java分布式应用配置动态刷新的方法及系统
CN117453380B (zh) 集群的容器组调度方法、系统以及计算机设备
US9378178B1 (en) Enhancing HTTP caching by allowing content sharing of data blocks across resources identified by different uniform resource locators
CN108073660B (zh) 一种实现缓存数据同步的方法及系统
CN112866356B (zh) Cdn缓存方法、装置及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16869668

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16869668

Country of ref document: EP

Kind code of ref document: A1