Streaming Web Page Generation for Fast Enterprise Site Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing static site generation and deployment systems are slow and inefficient for enterprise-scale websites due to long-running processes that cannot handle frequent data updates, making static generation infeasible for applications with high volumes of pages and frequent data changes.

Innovation Solution

A streaming static web page generation system that decouples the deployment process into three phases: initial build, page generation, and ongoing data update processing, utilizing stream processing to parallelize and optimize each phase for efficient and scalable web page generation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single build command is used to generate web pages from external data sources, then the deployment system can trigger builds in response to data changes, but the entire site must be regenerated each time, resulting in slow deployment for enterprise-scale websites with frequent updates

Engineering Contradiction:
Improvedeployment speedVSAvoidbuild time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the monolithic build process into three distinct phases: initial build phase (generating static assets and templates), page generation phase (creating individual web pages from templates and data streams), and data update processing phase (handling incremental data changes). This segmentation allows each phase to be optimized independently and enables parallel processing, dramatically reducing overall build time for enterprise-scale websites while maintaining the ability to respond to data changes.

Inventive Principle:
Principle #1Segmentation

2Reliability

If the deployment system regenerates the entire site on every data change, then data updates are reflected across all pages, but the process becomes infeasible for high-volume pages with frequent updates

Engineering Contradiction:
Improvedata update consistencyVSAvoidupdate throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by pre-generating static assets, templates, and page structures during the initial build phase before data changes occur. When data updates happen, the system only needs to apply incremental changes to the pre-generated structures rather than regenerating everything from scratch. This preliminary preparation enables rapid processing of data updates while ensuring consistency across all pages, making the system feasible for enterprise-scale websites with high update frequencies.

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If stream processing is used to parallelize page generation, then build-time performance improves, but the system complexity increases

Engineering Contradiction:
Improvebuild timeVSAvoidsystem complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent manages system complexity by clearly segmenting the build process into three phases with distinct responsibilities and data flows. Each phase produces well-defined outputs that serve as inputs to the next phase, creating a modular architecture that is easier to implement, maintain, and scale. The segmentation allows stream processing to be applied selectively in the page generation phase without complicating the entire system, as other phases can use traditional processing methods.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12511342B2Web site generation based on streams of data records
Publication Date: 2025.12.30 YEXT INC
  • US12511342B2 patent drawing
  • US12511342B2 patent drawing
  • US12511342B2 patent drawing

AI summary

A system and method to generate a website for a user system. A set of static assets associated with the website are generated. A first document of a first data record is transformed from a first schema to a second schema to generate a first transformed document. A data graph associated with the user system is generated, where the data graph includes the first transformed document and a portion of HTML, content of a data record received via a first data stream of a set of data streams. A web page including the portion of HTML content is rendered. The set of static assets and the web page of the website are provisioned to the user system.