Tablet Access Objects for Distributed Data Load Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed computing systems face inefficiencies when performing computations involving data stored in tables due to varied loads on servers and complex access control, leading to suboptimal performance and load imbalances.

Innovation Solution

A method and system that store table data structures in a file system with multiple tablets, each associated with distinct application and access objects, allowing for redistribution based on load-balancing criteria, enabling efficient data access and computational operations while co-locating application processing with data access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data is stored in multiple table portions across distributed servers, then data storage capacity and accessibility are improved, but system complexity and access control difficulty increase

Engineering Contradiction:
Improvedata storage capacityVSAvoidsystem complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent segments the distributed computing system into distinct table portions (tablets) that can be independently managed and accessed. Each tablet is a discrete unit of data storage that can be assigned to different servers, allowing the system to scale while maintaining manageable complexity through modular organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (the table access object and application object association mechanism) that manages the complexity of accessing distributed table portions. This intermediary handles the coordination between clients and multiple table portions, abstracting away the underlying system complexity while maintaining high storage capacity and accessibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If access to each table portion is controlled by separate processes on multiple servers, then data security and access control are improved, but operational complexity and access difficulty increase

Engineering Contradiction:
Improveaccess controlVSAvoidaccess difficulty
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent merges the access control functionality into a unified object-oriented structure where table access objects and application objects are associated in a systematic way. This combination maintains the distributed security model while simplifying access operations through consistent object interfaces that handle authentication and authorization transparently.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates universal object structures (table access objects and application objects) that can operate across all table portions regardless of which server hosts them. These multi-functional objects handle multiple operations (read, write, update) and work with any table portion, reducing the need for operation-specific code and simplifying the access process.

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

3Productivity

If load distribution across servers is optimized, then system performance and efficiency are improved, but redistribution complexity and management overhead increase

Engineering Contradiction:
Improvesystem efficiencyVSAvoidmanagement overhead
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements dynamic load balancing where table access objects and application objects can be redistributed among servers based on current system conditions. This dynamic approach allows the system to adapt to changing loads and optimize performance automatically, with the management overhead handled by the flexible object association mechanism rather than rigid configuration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent enables load optimization by changing the assignment parameters of object associations between tables and servers. By modifying which application objects are associated with which table access objects on which servers, the system can optimize performance without structural changes, using parameter adjustments rather than architectural redesign to manage complexity.

Inventive Principle:
Principle #35Parameter changes

4Speed

If application-specific computational operations are performed at data access points, then processing efficiency and speed are improved, but computational load and resource consumption increase

Engineering Contradiction:
Improvedata processing speedVSAvoidcomputational resource consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The patent applies local quality by enabling application-specific computational operations to be performed at the specific data access points where they are needed. Rather than centralizing all computation, the system allows each server to execute relevant application logic locally when accessing its hosted table portions, improving speed while distributing computational load appropriately across the system.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11822521B2Associating application-specific methods with tables used for data storage
Publication Date: 2023.11.21 GOOGLE LLC
  • US11822521B2 patent drawing
  • US11822521B2 patent drawing
  • US11822521B2 patent drawing

AI summary

A method of accessing data includes storing a table that includes a plurality of tablets corresponding to distinct non-overlapping table portions. Respective pluralities of tablet access objects and application objects are stored in a plurality of servers. A distinct application object and distinct tablet are associated with each tablet access object. Each application object corresponds to a distinct instantiation of an application associated with the table. The tablet access objects and associated application objects are redistributed among the servers in accordance with a first load-balancing criterion. A first request directed to a respective tablet is received from a client. In response, the tablet access object associated with the respective tablet is used to perform a data access operation on the respective tablet, and the application object associated with the respective tablet is used to perform an additional computational operation to produce a result to be returned to the client.