Hub Data Model for Registering Type Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity and cost of managing and storing large volumes of data across disparate storage systems, as well as the challenge of accessing and integrating data from multiple sources in real-time, pose significant technical hurdles.

Innovation Solution

A data processing system utilizing a hub data model to register additional type systems, enabling the creation and maintenance of materialized views that integrate data from multiple sources, while keeping the views up-to-date in near real-time without relocating the data from its optimized source storage locations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is stored across multiple disparate storage systems to optimize performance and features for individual data sets, then data storage performance and analysis benefits are improved, but system complexity and integration difficulty increase

Engineering Contradiction:
Improvedata storage performanceVSAvoidsystem integration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a view management system as an intermediary layer between applications and multiple disparate storage systems. This mediator handles data integration, type system registration, and cross-system queries automatically, eliminating the need for applications to directly manage complex integrations between different storage technologies while preserving the performance benefits of specialized storage for each data type.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If data is accessed from multiple different storage systems, then comprehensive data access is enabled, but operational complexity and implementation costs increase

Engineering Contradiction:
Improvedata access capabilityVSAvoidoperational complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The view management system provides universal data access capabilities across multiple disparate storage systems through a unified interface. It registers and manages multiple type systems corresponding to different storage technologies, enabling single point of access for comprehensive data retrieval without requiring separate integration logic for each storage system, thereby reducing operational complexity while maintaining versatile data access.

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

3Adaptability or versatility

If custom code is written to integrate data from multiple sources, then data integration functionality is achieved, but implementation costs and development time increase

Engineering Contradiction:
Improvedata integration capabilityVSAvoidimplementation cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The view management system enables self-service data integration by automatically registering type systems, managing materialized views, and handling cross-system data operations. Instead of requiring custom code for each integration scenario, the system provides automated mechanisms for defining views over multiple data sources, managing type mappings, and executing queries, thereby achieving versatile data integration while significantly reducing implementation costs and development effort.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12321335B2Registering additional type systems using a hub data model for data processing
Publication Date: 2025.06.03 AMAZON TECH INC
  • US12321335B2 patent drawing
  • US12321335B2 patent drawing
  • US12321335B2 patent drawing

AI summary

A new type system may be added to a type registry for a data processing service. A request to add the new type system may be received that describes the new type system for a data store. The new type system may be used to perform a data processing job that accesses the data store to obtain or store data as a source or target data store.