Asynchronous Resource Status Service via Cache

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing computing resources in network-based service provider networks is challenging due to difficulties in obtaining operational status information from numerous network services across different server computers in various data centers, often requiring long response times, which can lead to reduced network efficiency as client applications must maintain open connections.

Innovation Solution

Implementing a resource status service that asynchronously provides resource status data by using a cache to store data retrieved from network services, allowing clients to request status information without maintaining persistent connections, and providing partial results as they become available.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If synchronous requests are used to obtain resource status data from network services, then data accuracy is improved, but network responsiveness deteriorates due to long wait times

Engineering Contradiction:
Improvedata accuracyVSAvoidwait time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system pre-loads resource status data into a cache before it is actually needed. The resource status service continuously retrieves and stores status data from network services in advance, so when a client requests status information, the data is already available in the cache and can be returned immediately without waiting for synchronous network requests.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If persistent connections are maintained to obtain status data, then data completeness is improved, but network resource utilization deteriorates

Engineering Contradiction:
Improvedata completenessVSAvoidnetwork efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent introduces a resource status service as an intermediary layer between clients and network services. This service maintains the connection to network services and caches status data, allowing clients to request information without maintaining persistent connections. The intermediary handles the data retrieval and caching, freeing up network resources while ensuring data completeness through continuous background updates.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If status data is retrieved from multiple data centers, then data comprehensiveness is improved, but system complexity deteriorates

Engineering Contradiction:
Improvedata comprehensivenessVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges the data retrieval operations from multiple data centers into a single resource status service that handles all connections centrally. The service consolidates status data from various network services across different data centers into one unified cache, simplifying the client's interaction model. Clients only need to query the resource status service, which internally manages the complexity of retrieving and integrating data from multiple distributed sources.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10057365B1Asynchronous provision of resource status data
Publication Date: 2018.08.21 AMAZON TECH INC
  • US10057365B1 patent drawing
  • US10057365B1 patent drawing
  • US10057365B1 patent drawing

AI summary

Technologies are disclosed herein for asynchronous provision of resource status data. A resource status application can submit a request to a resource status service for status data regarding one or more computing resources provided by network services in a service provider network. In response thereto, the resource status service can submit synchronous requests to the network services for the status data. The resource status service can also provide a reply to the resource status application that includes an identifier (ID) that can be utilized to retrieve all or a portion of the status data at a future time. The reply might also specify a period of time that the resource status application is to wait before submitting another request for the status data to the resource status service. Subsequently, the resource status application can submit additional requests for the status data to the resource status service that include the identifier.