Spreadsheet-Style Database on Object Grid for Complex Event Processing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current database management systems lack the ability to efficiently integrate spreadsheet paradigms with object grids, limiting their capacity for complex event processing and data management across distributed systems.

Innovation Solution

A database management system is developed that maps a database onto an object grid, utilizing a spreadsheet paradigm where messages are routed through the object grid backbone, allowing interactions with spreadsheet applications via structured data messages, enabling complex event processing and efficient data management by leveraging the object grid's redundancy and fault tolerance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a traditional database management system is used, then data storage and retrieval functions are provided, but the ability to efficiently integrate spreadsheet paradigms with object grids is lacking

Engineering Contradiction:

Improveintegration capabilityVSAvoidsystem architecture

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The database management system is enhanced to perform multiple functions by integrating spreadsheet paradigm capabilities with object grid operations. The system can now handle both traditional database operations and spreadsheet-like data manipulation, allowing a single system to serve diverse data management needs without requiring separate specialized systems.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

A message routing mechanism acts as an intermediary between the object grid backbone and spreadsheet applications. This mediator translates and directs messages containing database commands, target arrays, and data objects between different system components, enabling seamless integration without direct complex point-to-point connections.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If spreadsheet paradigm integration is added to enhance adaptability, then complex event processing capability improves, but system complexity increases

Engineering Contradiction:

Improvecomplex event processing capabilityVSAvoidsystem structure

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system architecture is segmented into distinct functional components: the object grid backbone for data storage and retrieval, the message routing layer for communication coordination, and the spreadsheet application layer for data manipulation. This segmentation allows complex event processing capabilities to be added without monolithically increasing overall system complexity, as each component can be developed and maintained independently.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The message routing mechanism serves as an intermediary that manages communication between components, handling the complexity of coordinating complex event processing across the distributed system. This mediator abstracts the complexity from individual components, allowing them to focus on their specific functions while the routing layer manages the overall coordination.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Measurement precision

If structured data message format with target arrays is used, then precise cell addressing is achieved, but message format complexity increases

Engineering Contradiction:

Improvecell addressing precisionVSAvoidmessage format

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The message format utilizes parameter changes by representing target arrays through transformations of the spreadsheet data structure. Instead of complex absolute addressing, the system uses relative addressing with offset parameters from a base cell, allowing precise cell identification through simpler parameter variations rather than complex coordinate systems.

Inventive Principle:

Principle #35Parameter changes

4Reliability

If object grid backbone is deployed for high availability, then data redundancy and fault tolerance improve, but system infrastructure complexity increases

Engineering Contradiction:

Improvedata availabilityVSAvoiddistributed system infrastructure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The object grid backbone implements self-service mechanisms where nodes automatically perform data replication, fault detection, and failover operations without requiring complex external management. Each node in the distributed system autonomously contributes to maintaining data redundancy and availability, reducing the need for complex centralized infrastructure management while achieving high reliability.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS10031904B2Database management system based on a spreadsheet concept deployed in an object grid

Publication Date: 2018.07.24 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A method for interacting with a database stored in an object grid is described. The database is given attributes of a spreadsheet. Elements stored in the database are represented and addressed as cells of a spreadsheet. Cells can store data objects, including formulas, and executable scripts. The spreadsheet can evaluate formulas, carry out the program instructions of executable scripts, and perform complex event processing. Interaction with the spreadsheet is accomplished through the use of structured data messages which include instructions, spreadsheet and cell addressing and, optionally, data elements.