Application Metadata Management via Real-Time Caching

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Writing software, especially web-based applications, is a complex, error-prone, time-consuming, and costly process that often requires a team of skilled professionals, making it inaccessible to smaller entities or solo developers due to budget and expertise constraints.

Innovation Solution

A computer-implemented method and system for managing application entities, allowing users to configure applications using pre-written functions and entities without writing code, enabling rapid development and deployment of reliable, enterprise-scale software applications through a configuration platform that automates metadata generation and caching for real-time updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional software development methods are used, then application quality and security standards are met, but development time and cost increase significantly

Engineering Contradiction:

Improveapplication quality and security standardsVSAvoiddevelopment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system pre-generates application metadata, including security configurations and quality standards, before the actual application development process. This preliminary preparation of development artifacts enables smaller teams to start with enterprise-grade foundations already in place, reducing the time needed to achieve compliance and quality standards.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses templates and pre-defined metadata schemas that can be copied and adapted for different applications. These templates encode best practices for security and quality, allowing developers to replicate enterprise standards across multiple projects without reinventing the wheel, thus maintaining high standards while reducing development time.

Inventive Principle:

Principle #26Copying

2Reliability

If traditional software development methods are used, then application quality and security standards are met, but resource requirements and cost increase

Engineering Contradiction:

Improveapplication quality and security standardsVSAvoidresource requirements

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

Pre-generated metadata and templates encode enterprise security and quality standards that can be copied across projects. This allows smaller teams with limited resources to access and reuse proven standards rather than developing them from scratch, maintaining high reliability with reduced resource investment.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system transforms complex development requirements into standardized metadata parameters that can be automatically processed. By changing the representation of development artifacts from raw code to structured metadata, the system reduces the manual expertise and resources needed while maintaining quality and security standards.

Inventive Principle:

Principle #35Parameter changes

3Stability of the object's composition

If real-time metadata updates are provided to all active sessions, then application consistency is maintained, but network bandwidth and server load increase

Engineering Contradiction:

Improveapplication consistencyVSAvoidnetwork bandwidth

Core Design Contradiction:

Stability of the object's compositionVSUse of energy by moving object

Solution Approach 1:

The system implements selective metadata broadcasting that sends updates only to sessions that need them, rather than flooding all active sessions with every change. This partial action approach maintains application consistency for relevant users while significantly reducing unnecessary network traffic and server load compared to universal broadcasting.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The system applies different update strategies to different user sessions based on their specific needs and context. Rather than uniform treatment, each session receives metadata updates tailored to its requirements, maintaining consistency where needed while conserving network resources where full synchronization is not necessary.

Inventive Principle:

Principle #3Local quality

4Productivity

If comprehensive application metadata is stored in read-optimized storage, then application performance is improved, but storage infrastructure complexity increases

Engineering Contradiction:

Improveapplication performanceVSAvoidstorage infrastructure complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system segments metadata into different categories and stores them in appropriately optimized storage locations. By dividing the metadata storage into functional segments (e.g., frequently accessed vs. archival data), the system achieves high performance for critical operations without requiring the entire infrastructure to be complex read-optimized storage, thus balancing performance with infrastructure simplicity.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11886434B1Management of application entities

Publication Date: 2024.01.30 BILDR INC

AI summary

A computer-implemented method performed by at least one processor includes actions of: receiving information indicating a change to an entity of an application; and in response to receiving the information: providing, in real-time, the information indicating the change to the entity as one or more items of application metadata to one or more active sessions of the application; storing the information indicating the change to the entity as one or more items of application metadata in read-optimized storage; and storing one or more timestamps corresponding to the one or more items of application metadata in a timestamp cache.