Surrogate Content Service for Server Unavailability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Servers in computer networks often become unavailable due to heavy loads or latency issues, leading to errors and prolonged recovery times, as they continue to receive requests that further delay recovery.

Innovation Solution

A surrogate content service is implemented, which generates pre-computed backup resources and redirects requests to these resources when the primary content sources are unavailable, using a proxy server and backup content generator to manage resource requests and traffic efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If servers continue to receive requests during unavailability, then request processing continues, but recovery time is prolonged

Engineering Contradiction:
Improverequest processing continuityVSAvoidrecovery time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

A surrogate server acts as an intermediary between clients and unavailable content servers. The surrogate receives requests when content servers are unavailable and responds with placeholder content or error pages, preventing requests from reaching the failing servers and allowing them to recover without processing additional requests.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system proactively detects server unavailability and redirects requests to surrogate servers before the content servers can process additional requests. This preliminary action stops the harmful accumulation of requests on failing servers, enabling faster recovery.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If servers are under heavy load, then service availability is maintained, but latency increases and failures occur

Engineering Contradiction:
Improveservice availabilityVSAvoidresponse latency
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The surrogate server mediates between clients and overloaded content servers by absorbing excess requests and providing placeholder responses. This reduces the effective load on content servers during high-traffic periods, preventing latency-induced failures while maintaining service availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If backup content is generated continuously, then availability during failures is improved, but system complexity and resource consumption increase

Engineering Contradiction:
Improvecontent availability during failureVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of continuously generating and storing full backup copies of all content, the system creates simple placeholder responses (surrogate content) that indicate the original content is unavailable. This copying approach maintains availability during failures without the complexity of managing comprehensive backup inventories.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system extracts only the essential function of content availability during failures, implementing it through simple placeholder responses rather than complete content backups. This removes the complex infrastructure of full content replication while maintaining the core reliability benefit.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10503613B1Efficient serving of resources during server unavailability
Publication Date: 2019.12.10 AMAZON TECH INC
  • US10503613B1 patent drawing
  • US10503613B1 patent drawing
  • US10503613B1 patent drawing

AI summary

Systems and methods are provided for efficiently providing backup resources during server unavailability. Server unavailability includes server unresponsiveness and latency. The system and methods generate backup resources that can be provided to clients during server unavailability. The backup resources may be static versions of dynamically generated resources that rely on multiple services. The generation of backup resources can be prioritized based on a determination of the frequently accessed resources. During failure scenarios, the systems and methods can monitor and redirect traffic as needed to improve server recovery times.