Commerce Platform Traffic Surge Protection via Static Package

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

E-commerce platforms face challenges in managing surges in network traffic, which can overwhelm backend systems and lead to costly and error-prone infrastructure management, especially during high-demand events like flash sales, as existing technologies struggle to scale and differentiate legitimate traffic from illegitimate traffic.

Innovation Solution

A network traffic surge-resistant platform is implemented, where a static package containing interface information and transaction data is stored in networked storage, allowing customer computers to render the interface and manage inventory without overwhelming server resources, with authentication managed through two-factor authentication using one-time passwords sent via different communication mediums.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the e-commerce platform handles surge network traffic by processing all customer requests through backend servers, then complete transaction processing is achieved, but backend systems become overwhelmed and cannot handle the massive volume of queries

Engineering Contradiction:

Improvesystem stability during traffic surgeVSAvoidtransaction processing capacity

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system segments transaction processing into two parts: (1) interface rendering and cart management are handled locally by the customer's browser using a static package, and (2) only essential backend operations (payment processing and inventory reservation) are performed on the server. This segmentation reduces the load on backend systems while maintaining complete transaction functionality.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The customer's browser performs self-service by rendering the interface and managing cart operations locally without requiring continuous server communication. The static package enables the browser to function independently for most operations, reducing dependency on overloaded backend systems during traffic surges.

Inventive Principle:

Principle #25Self-service

2Use of energy by stationary object

If the platform configures infrastructure to handle mean site traffic, then server resources are efficiently utilized for normal operations, but the system cannot handle relatively infrequent surges of high network traffic volume

Engineering Contradiction:

Improveserver resource utilizationVSAvoidtraffic volume handling capacity

Core Design Contradiction:

Use of energy by stationary objectVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary action by generating a static package that contains all interface rendering information and transaction data needed for the offer. This package is prepared in advance and stored in networked storage, enabling customers to render the interface locally without requiring server resources during the traffic surge event.

Inventive Principle:

Principle #10Preliminary action

3Ease of manufacture

If backend systems are built with older technology, then initial system deployment is simpler and less costly, but the systems cannot handle the massive volume of queries into databases during high traffic events

Engineering Contradiction:

Improvesystem deployment simplicityVSAvoiddatabase query handling capacity

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The system extracts the interface rendering function from the backend system and places it in the static package that runs locally in the browser. This extraction removes the burden of rendering complex interfaces from the backend servers, allowing them to focus only on essential data operations even with older technology.

Inventive Principle:

Principle #2Taking out (Extraction)

4Measurement precision

If the platform makes multiple backend calls during interface rendering and cart management, then real-time data accuracy is maintained, but network traffic and server load increase significantly

Engineering Contradiction:

Improveinventory data accuracyVSAvoidnetwork traffic volume

Core Design Contradiction:

Measurement precisionVSLoss of energy

Solution Approach 1:

The system creates a copy of the offer data in the static package that can be used for interface rendering and cart management. This copy allows the browser to perform operations locally without continuously querying the backend for real-time data, significantly reducing network traffic while maintaining functional accuracy.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS11636512B1Inventory management system protection for network traffic surge resistant platform

Publication Date: 2023.04.25 FEVO INC

AI summary

A network traffic surge resistant platform is described herein. An example system includes a network storage, and one or more servers configured as a commerce platform including an authentication manager. The commerce platform generates a first secret code and sends the first secret code via a first communication medium associated with a first identifier. The commerce platform also generates a second secret code and sends the second secret code via a second communication medium associated with a second identifier. In response to determining the first input code matching the first secret code and the second input code matching the second secret code, the commerce platform authorizes a transaction associated with a particular browser and associates the transaction with a customer record associated with both the first and second identifiers.