Database Migration Recommendations for Cloud Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Migrating database applications to cloud computing systems is challenging due to data consistency requirements, which can lead to performance degradation in distributed environments, as requests to read data must wait for writes to be replicated across multiple servers, causing delays and inefficiencies.

Innovation Solution

A computer-implemented method and system that determines possible transactions and application requirements for a database application, generating migration recommendations to ensure compliance with consistency, performance, and storage requirements by mapping transactions to appropriate cloud computing instances, and modifying recommendations to split or retain transaction groups based on these requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If database applications are migrated to distributed cloud computing systems, then scalability and resource utilization are improved, but data consistency requirements cause performance degradation due to replication delays

Engineering Contradiction:
Improvecloud migration capabilityVSAvoiddata access performance
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the database application into multiple transactions and groups them based on data consistency requirements. Transactions that require strong consistency are kept together on the same cloud computing instance, while transactions with weaker consistency requirements can be distributed across different instances. This segmentation allows the system to leverage cloud scalability while maintaining performance for consistency-critical operations.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If transactions are distributed across multiple cloud computing instances, then resource utilization and scalability are improved, but data consistency cannot be guaranteed without replication delays

Engineering Contradiction:
Improvedistributed execution capabilityVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies local quality by assigning different consistency guarantees to different transaction groups based on their specific requirements. Transactions grouped together share the same consistency level, allowing the system to provide strong consistency where needed while enabling greater distribution and scalability where weaker consistency is acceptable. This differentiated approach resolves the contradiction between distribution and consistency.

Inventive Principle:
Principle #3Local quality

3Reliability

If read requests wait for write replication across multiple servers, then data consistency is maintained, but request processing time increases

Engineering Contradiction:
Improvedata consistencyVSAvoidrequest processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements partial action by having read requests wait for write replication only when necessary - specifically when the read and write operations belong to the same consistency group. For transactions in different groups or with weaker consistency requirements, reads can proceed without waiting for full replication, thus reducing processing time while maintaining consistency where required.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9703811B2Assessing database migrations to cloud computing systems
Publication Date: 2017.07.11 ACCENTURE GLOBAL SERVICES LTD
  • US9703811B2 patent drawing
  • US9703811B2 patent drawing
  • US9703811B2 patent drawing

AI summary

This disclosure relates to assessing database migrations to cloud computing systems. On example method includes determining, by a migration server including one or more hardware processors, a set of possible transactions associated with a database application based at least in part on a set of application attributes associated with the database application; generating, by the migration server, a set of application requirements associated with the set of possible transactions; and creating, by the migration server, a set of migration recommendations associated with the database application based on the set of application requirements, the set of migration recommendations configured to allow the database application to be migrated to a cloud computing system and to allow the database application to comply with the set of application requirements when executed in the cloud computing system.