Resilient Application Data Mirroring Across Distinct Clusters

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing computer systems face challenges in maintaining resilient operation of software applications across operationally distinct clusters, particularly in ensuring consistent data responses and fault tolerance in case of cluster failures.

Innovation Solution

The method involves operating multiple instances of a software application in distinct clusters, assessing streaming architecture requirements, creating and mirroring application data versions, and synchronizing indexes to ensure consistent responses across clusters, with real-time mirroring and local storage of data to maintain resilience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple instances of software application are operated in operationally distinct clusters, then resilience and fault tolerance are improved, but device complexity increases

Engineering Contradiction:

ImproveresilienceVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system segments application data into multiple versions (main version and replica versions) that can be independently managed across different clusters. Each cluster maintains its own instance of the software application with access to localized data versions, enabling independent operation and failure isolation while maintaining overall system resilience.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements copying by creating replica versions of application data that mirror the main version stored in databases. These replica versions are transmitted to operationally distinct clusters, allowing each cluster to have its own copy of the data for continuous operation even if the source cluster fails.

Inventive Principle:

Principle #26Copying

2Reliability

If replica versions of application data are created and mirrored across clusters, then fault tolerance is improved, but loss of time increases

Engineering Contradiction:

Improvefault toleranceVSAvoiddata synchronization time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-creating and pre-positioning replica versions of application data in operationally distinct clusters before failures occur. This advance preparation ensures that when a cluster fails, the replica data is already available for immediate use, minimizing downtime and avoiding the need for real-time data recovery operations.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent ensures continuity of useful action by implementing real-time mirroring mechanisms that continuously synchronize data between clusters. The replica versions are updated in real-time alongside the main version, ensuring that data is always current and available for continuous operation without interruption even during cluster failures.

Inventive Principle:

Principle #20Continuity of useful action

3Reliability

If real-time mirroring of application data is implemented, then consistent responses across clusters are improved, but use of energy increases

Engineering Contradiction:

Improveresponse consistencyVSAvoidenergy consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies local quality by storing and processing data locally within each cluster rather than requiring all data to be accessed from a central source. Each cluster maintains its own replica versions and indexes locally, enabling independent data processing and reducing the need for continuous inter-cluster communication, thereby lowering overall energy consumption while maintaining response consistency.

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS11422796B2Computer-based systems configured to generate and/or maintain resilient versions of application data usable by operationally distinct clusters and methods of use thereof

Publication Date: 2022.08.23 CAPITAL ONE SERVICES LLC

AI summary

Systems and methods associated with generating and/or maintaining resilient versions of application data usable by operationally distinct clusters are disclosed. In one embodiment, an exemplary method may comprise operating plural instances of a software application in a first cluster and a second cluster, assessing requirements of streaming architecture of both clusters that impact the instances' ability to process application data, creating at least two versions of the application including a main version in one cluster and a replica version for an operationally distinct cluster, automatically mirroring replica versions of the application data from each cluster into a distinct cluster for access and use by the software instance in the distinct cluster, and storing indexes for main and replica versions and all data that the software application requires to provide consistent responses in all such operationally distinct clusters.