Hot-Cold Product Indexing for E-commerce Database Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

E-commerce database systems face performance issues due to increased latency as the number of products grows, leading to slow search engine performance, and existing strategies for indexing products are inefficient, resulting in high Type-II errors and increased latency when accessing 'cold' items.

Innovation Solution

Implementing a prioritized product index structure by dividing products into 'hot' and 'cold' clusters based on predicted access likelihood, using a machine learning model to classify products and adjust cluster assignments dynamically, with a cost-sensitive algorithm to minimize errors and optimize resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If the number of products in the database system increases, then the product variety and selection improve, but the database system performance deteriorates due to increased latency

Engineering Contradiction:
Improvenumber of productsVSAvoiddatabase access latency
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent divides the database system into two separate database clusters: a first database cluster for 'hot' items (frequently accessed products) and a second database cluster for 'cold' items (infrequently accessed products). This segmentation allows the system to handle different access patterns efficiently, reducing overall latency while maintaining large product inventory. The hot cluster uses optimized indexing and caching strategies for fast access, while the cold cluster stores less frequently accessed items without compromising system performance.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If traditional indexing strategies are used for all products, then the database structure remains simple, but search engine performance deteriorates due to high Type-II errors and increased latency

Engineering Contradiction:
Improveindexing structure complexityVSAvoidsearch engine performance
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent applies different indexing and storage strategies to different portions of the database based on access patterns. The first database cluster (hot items) implements optimized indexing structures with higher redundancy and faster access paths, while the second database cluster (cold items) uses more compact storage. This local differentiation of quality and structure optimizes search performance for frequently accessed items without unnecessarily complicating the entire database system.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically classifies items as 'hot' or 'cold' based on access patterns and transitions items between database clusters accordingly. This dynamic approach allows the indexing structure to adapt to changing access patterns, improving search engine performance by ensuring that currently popular items are always in the optimized hot cluster with fast access paths.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10628446B2System and method for integrating business logic into a hot/cold prediction
Publication Date: 2020.04.21 WALMART APOLLO LLC
  • US10628446B2 patent drawing
  • US10628446B2 patent drawing
  • US10628446B2 patent drawing

AI summary

A system and method for integrating business logic into a database system is disclosed herein. One or more processing modules; and one or more non-transitory memory storage modules storing computing instructions configured to run on the one or more processing modules and perform: providing a set of distinct records in a database system, the database system comprising a first database cluster H and a second database cluster L, wherein each record of the set of distinct records represents an item for online sale, and wherein the first database cluster H has higher processing capabilities than the second database cluster L; receiving a search request from a requester; comparing the each record of the set of distinct records to a white-list database, wherein one or more records in the white-list database are predicted to be accessed by most requests from other requests within the set of distinct records in the database system; when a first record of the set of distinct records is contained in the white-list database, placing the first record in the first database cluster H; when a second record of the set of distinct records is not contained in the white-list database, calculating a probability that the second record will be accessed and (a) placing the second record of the set of distinct records in the first database cluster H and adding the second record to the white-list database when the second record is likely to be accessed, or (b) placing the second record of the set of distinct records in the second database cluster L when the second record is not likely to be accessed; and presenting a search result containing one or more records of the set of distinct records to the requester. Other embodiments are disclosed herein.