Big Data Processing Framework for Shuffle and Sort Bottlenecks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Big Data processing technologies face challenges in efficiently handling large event streams, data aggregation, and non-linear operations, such as reducers, shuffles, and sorts, due to reliance on outdated principles like scale-out on commodity processors, moving compute to data, and pluggable file formats, leading to inefficiencies and high costs.

Innovation Solution

A Big Data processing framework that inverts traditional principles by prioritizing scale-up on high-core-count processors before scale-out, moving data to compute nodes via high-bandwidth cloud storage networks, and utilizing optimized file formats like Avro and Parquet with specialized processing techniques to enhance efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If traditional scale-out on commodity processors is used, then system capacity increases, but processing efficiency deteriorates due to non-linear operations overhead

Engineering Contradiction:
Improvesystem capacityVSAvoidprocessing efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent inverts the traditional approach by moving data to compute nodes instead of moving compute to data. This reversal eliminates the overhead of non-linear operations like reducers, shuffles, and sorts that plague traditional scale-out systems, thereby maintaining processing efficiency while scaling system capacity.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent changes the fundamental parameter of data location from distributed storage to centralized compute-node storage. By altering where data resides (on compute nodes rather than distributed across the network), the system eliminates the performance degradation associated with traditional scale-out approaches while maintaining increased system capacity.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If pluggable file formats are used, then system versatility increases, but processing speed deteriorates due to decoding and re-encoding overhead

Engineering Contradiction:
Improvesystem versatilityVSAvoidprocessing speed
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The patent applies preliminary action by pre-encoding data into optimized binary formats before storage. This eliminates the need for decoding and re-encoding during processing operations, thereby maintaining system versatility while dramatically improving processing speed through the elimination of repetitive encoding/decoding cycles.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses disposable, format-specific optimized libraries for each file format type. Instead of maintaining a single pluggable interface with universal decoding/encoding capabilities, the system employs specialized, highly optimized libraries that are discarded and replaced based on the specific format being processed, eliminating the overhead of generic format handling.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

3Productivity

If data is grouped and joined at tens of billions of events per day, then data aggregation capability increases, but system reliability deteriorates due to crashes

Engineering Contradiction:
Improvedata aggregation capabilityVSAvoidsystem reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent extracts the problematic collating join operation from the traditional data processing pipeline. By removing the need to group and join data at such high volumes through traditional reducers, the system eliminates the source of crashes and reliability issues while maintaining the ability to aggregate tens of billions of events per day.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary approach where data is processed and staged in optimized formats before final aggregation. This intermediary processing step prevents the direct collision of massive data volumes that causes crashes in traditional systems, thereby maintaining high data aggregation capability while improving system reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If decoding and re-encoding of all data is performed, then format flexibility is maintained, but resource efficiency deteriorates due to garbage collection pressure

Engineering Contradiction:
Improveformat flexibilityVSAvoidresource efficiency
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent applies preliminary action by pre-encoding data into optimized binary formats before storage. This eliminates the need for decoding and re-encoding during processing operations, thereby maintaining system versatility while dramatically improving processing speed through the elimination of repetitive encoding/decoding cycles.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the fundamental parameter of data location from distributed storage to centralized compute-node storage. By altering where data resides (on compute nodes rather than distributed across the network), the system eliminates the performance degradation associated with traditional scale-out approaches while maintaining increased system capacity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20260037336A1Big Data processing platform and method
Publication Date: 2026.02.05 JAYE DANIEL
  • US20260037336A1 patent drawing
  • US20260037336A1 patent drawing
  • US20260037336A1 patent drawing

AI summary

A highly efficient, scalable, and adaptable framework suitable for modern Big Data processing challenges in cloud-based environments. The framework preferably leverages a scale-up before scale-out paradigm that prioritizes scaling up individual nodes (e.g., with high-core-count processors) before scaling out across multiple nodes. In addition, preferably the framework moves data to compute nodes, e.g., utilizing high-bandwidth cloud storage networks for efficient data transfer. Further, the framework preferably employs specialized primitives optimized for specific Big Data processing tasks, particularly for collations, sorts, and shuffles. Finally, framework utilizes optimized libraries for a small number of file formats.