Distributed Database Service Segmentation for Reliability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional systems for processing web-based database requests often fail to operate reliably and efficiently, leading to service errors and a lack of scalability, fault tolerance, and high availability, especially in cloud-based environments.

Innovation Solution

A distributed computer system capable of servicing web-based database service requests, featuring a NoSQL Key/Value Store database that supports various configurations, including active/active and active/standby modes, with features like data replication, encryption, and security mechanisms, allowing for flexible scaling and high availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional systems process web-based database requests, then basic database operations can be performed, but the systems fail to operate reliably and efficiently, leading to service errors

Engineering Contradiction:

Improvesystem reliabilityVSAvoidrequest processing efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system segments the database service into multiple independent database service entities (DB2 subsystems) that can operate autonomously. Each entity handles specific database requests, and if one fails, others continue operating. This segmentation resolves the contradiction by improving reliability through distribution while maintaining processing efficiency through parallel operation of multiple entities.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system changes the operational parameters by implementing dynamic request routing and load distribution across multiple database service entities. By adjusting how requests are distributed and managed across entities, the system achieves both high reliability (through redundancy) and high efficiency (through optimized request handling), resolving the apparent contradiction between reliability and productivity.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If a single database service entity handles requests, then the system is simple to manage, but it lacks scalability and fault tolerance

Engineering Contradiction:

ImprovescalabilityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Multiple database service entities are configured to perform the same universal database service functions. Each entity can independently handle various types of database requests (SQL, non-SQL, different protocols), providing scalability through added capacity while maintaining manageable complexity through standardized, repeatable configurations across entities.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system creates multiple copies of the database service entity, each capable of independent operation. These copied entities provide scalability by increasing system capacity while managing complexity through consistent replication of proven, working configurations. The copying approach allows linear scaling without proportionally increasing operational complexity.

Inventive Principle:

Principle #26Copying

3Reliability

If database service entities are distributed across multiple systems, then fault tolerance improves, but system complexity increases

Engineering Contradiction:

Improvefault toleranceVSAvoiddistributed system complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

Multiple database service entities are merged into a coordinated distributed system with unified request routing and management. The entities share common configuration management, monitoring, and request distribution mechanisms, which reduces the complexity overhead of distribution while maintaining the fault tolerance benefits of having multiple independent entities across different systems.

Inventive Principle:

Principle #5Merging (Combining)

4Reliability

If the system processes all database requests through a single entity, then transaction commitment is simplified, but high availability cannot be achieved

Engineering Contradiction:

Improvehigh availabilityVSAvoidtransaction management simplicity

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

An intermediary request routing mechanism is introduced that directs database requests to appropriate service entities and manages transaction coordination across entities. This intermediary layer maintains operational simplicity by abstracting the complexity of distributed transaction management, while enabling high availability through intelligent request routing to healthy entities and automatic failover capabilities.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10671695B2System and method for storing and processing database requests

Publication Date: 2020.06.02 WALMART APOLLO LLC

AI summary

A system is provided that is adapted to service web-based database service requests. In one implementation, a database service is provided for servicing web-originated service requests. In one implementation, virtual computer systems may be used to service requests in a more reliable manner Different operating modes may be configured for backup redundancy and the database service may be scaled to meet service requests for a particular application. Also, methods are provided for exchanging timestamp information among web service transaction systems to reduce the amount of processing capability and bandwidth for ensuring database consistency. Further, a NoSQL Key/Value (KVS) database is provided that provides one or more features that may be beneficial for cloud service, Internet-based, and other types of database applications.