CDN Edge Transaction Processing to Cut Origin Server Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional systems require clients to communicate directly with an origin server for transaction processing, leading to high latency and potential overload during peak periods, which can degrade the user experience.

Innovation Solution

Transaction processing is performed at edge servers within a content distribution network (CDN), reducing backend calls and enabling faster transaction completion by utilizing dedicated high-speed connections to transaction sites, thereby alleviating the origin server from handling these requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If clients communicate directly with origin servers for transaction processing, then transaction processing can be performed, but latency increases and origin servers become overloaded during peak periods

Engineering Contradiction:
Improvetransaction processing reliabilityVSAvoidtransaction latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces edge servers as intermediary components between clients and origin servers. These edge servers handle transaction processing requests locally, acting as mediators that prevent direct client-origin server communication during peak periods. The edge servers maintain connection pools to transaction entities and can process transactions independently, reducing latency while maintaining reliability through distributed processing across multiple edge servers.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If origin servers handle all transaction processing requests, then complete transaction processing capability is maintained, but server overload occurs during high-traffic periods

Engineering Contradiction:
Improvetransaction processing capacityVSAvoidsystem stability under load
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the transaction processing function by distributing it across multiple edge servers located at different points of presence within the CDN network. Each edge server can independently handle a portion of the transaction load, maintaining overall system capacity while preventing any single origin server from becoming overloaded. This segmentation enables horizontal scaling and improves system stability under high traffic conditions.

Inventive Principle:
Principle #1Segmentation

3Loss of time

If edge servers process transactions locally, then latency is reduced and origin servers are relieved, but edge servers require dedicated connections to transaction entities

Engineering Contradiction:
Improveperceived latencyVSAvoidedge server connection infrastructure
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent implements connection pools at edge servers that can be shared across multiple clients and transactions. These pooled connections to transaction entities serve multiple purposes simultaneously, reducing the need for dedicated connections for each transaction. The connection pools are managed centrally at edge servers, allowing efficient reuse of network resources while maintaining low latency for local transaction processing.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12567095B2Transaction processing at edge servers in a content distribution network
Publication Date: 2026.03.03 AMAZON TECH INC
  • US12567095B2 patent drawing
  • US12567095B2 patent drawing
  • US12567095B2 patent drawing

AI summary

Various embodiments of apparatuses and methods for transaction processing at edge servers in a content distribution network (“CDN”) are described. In some embodiments, an edge server receives an initial request from a client for content associated with a particular origin, and then provides the content to the client. The edge server can then receive another request from the client that might include an indicator for transaction processing. The edge server determines that transaction processing is indicated for handling this new request, in some embodiments. The edge server can then send a transaction notification to the origin, receive a transaction continuation response from the origin, and then execute a data transaction with transaction entities that are distinct from the content distribution network and the origin, in some embodiments. If the transaction is successful, the edge server can notify the client and the origin of the successful transaction, in some embodiments.