Schemaless Datastore Constraint Enforcement via Intermediary Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional schemaless datastores lack the ability for application developers and domain administrators to impose predefined constraints on data operations, making it difficult to manage and enforce data integrity across multiple instances of applications or different applications within a domain.

Innovation Solution

A system and method for processing data requests at a schemaless datastore that analyzes requests for constraint-restricted portions, retrieves and applies predefined constraints, and enforces these constraints before executing the requests, using a process running on the server system, a sandboxed environment, or the datastore itself.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If schemaless datastores are used to efficiently store and manage large quantities of data, then data management efficiency is improved, but the ability to impose predefined constraints on data operations is lost

Engineering Contradiction:
Improvedata management efficiencyVSAvoiddata integrity constraint enforcement
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces an intermediary layer between the application and the schemaless datastore that handles constraint enforcement. This intermediary component translates high-level data requests into constrained operations, allowing the schemaless datastore to maintain its efficiency while the intermediary ensures data integrity through predefined constraints. The intermediary acts as a mediator that preserves the flexibility of schemaless storage while adding the necessary constraint enforcement capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple instances of applications run in parallel to provide additional bandwidth, then request handling capacity is improved, but constraint management complexity increases

Engineering Contradiction:
Improverequest handling capacityVSAvoidconstraint management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal constraint management system that serves multiple application instances through a shared constraint repository and enforcement mechanism. Instead of each application instance maintaining its own constraints, the system provides a unified interface where constraints are defined once and automatically applied across all parallel instances. This universal approach allows the system to handle requests from multiple instances while maintaining consistent constraint enforcement, thereby reducing management complexity despite increased request handling capacity.

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

3Stability of the object's composition

If domain administrators can impose constraints on multiple applications within a domain, then data consistency across applications is improved, but system complexity increases

Engineering Contradiction:
Improvedata consistency across applicationsVSAvoidconstraint imposition system complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent segments the constraint management system into distinct modular components: a constraint definition interface for administrators, a constraint repository for storage, and an enforcement engine for application. This segmentation allows domain administrators to impose constraints on multiple applications within a domain through a structured, step-by-step process. Each component handles a specific aspect of constraint management, reducing overall system complexity while enabling comprehensive data consistency enforcement across applications.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9465837B1Processing data requests for a schemaless datastore in accordance with constraint information
Publication Date: 2016.10.11 GOOGLE LLC
  • US9465837B1 patent drawing
  • US9465837B1 patent drawing
  • US9465837B1 patent drawing

AI summary

A server system having memory and one or more processors analyzes a first data request associated with a first application, where the analyzing includes determining whether the first data request is associated with a constraint-restricted portion of a schemaless datastore in which data operations are subject to a set of predefined constraints. In accordance with a determination that the first data request is associated with the constraint-restricted portion, the server system retrieves constraint information corresponding to the set of predefined constraints and processes the first data request in accordance with the constraint information, where the constraint information enables the set of predefined constraints to be applied to the first data request prior to execution of the first data request.