Data Source Wrapper for Transparent Connection Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data source management tools are invasive, non-transparent, and lack extensibility, often requiring code changes and failing to provide compatibility with various applications and data sources, making them complex to implement and use.

Innovation Solution

A system and method for data source management using custom data sources, which creates a custom data source in response to requests and employs configuration modules for handling connections, ensuring transparency and extensibility by dynamically creating or pre-existing custom data sources with tailored configurations for load balancing, fail-over, and throttle management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing data source management tools are used, then data source connections can be managed, but the tools are invasive and require code changes in applications or application servers

Engineering Contradiction:

Improvedata source connection managementVSAvoidimplementation complexity

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The patent introduces a data source wrapper as an intermediary layer between applications and data sources. This wrapper encapsulates the complexity of connection management, load balancing, and failover logic, allowing existing applications to interact with data sources through a standardized interface without requiring invasive code changes. The wrapper acts as a mediator that translates application requests into appropriate data source operations.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments data source management functionality into separate, modular components including the data source wrapper, connection pool manager, and configuration files. This segmentation allows each component to be developed, deployed, and maintained independently, reducing implementation complexity and enabling gradual adoption without requiring comprehensive system reconfiguration.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If existing data source management tools are used, then connections can be controlled, but the tools lack extensibility and compatibility with various applications and data sources

Engineering Contradiction:

Improvecompatibility with applications and data sourcesVSAvoidsystem architecture

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The data source wrapper is designed as a universal interface that can work with multiple types of data sources (relational databases, NoSQL databases, file systems) and various application types (web applications, enterprise applications, mobile applications). The wrapper implements a standardized set of methods and properties that provide consistent functionality across different data source types, eliminating the need for application-specific management tools for each data source type.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses configuration files with adjustable parameters to adapt the wrapper's behavior to different data sources and applications. By changing configuration parameters rather than modifying the underlying system architecture, the same wrapper implementation can serve multiple purposes and accommodate various data source types, reducing architectural complexity while maintaining versatility.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If management tools alter SQL code or application code, then connection management is achieved, but the process becomes invasive and difficult to implement

Engineering Contradiction:

Improveconnection management controlVSAvoidimplementation simplicity

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

Rather than altering existing SQL or application code, the patent introduces a data source wrapper as an intermediary that sits between the application and the data source. This wrapper intercepts and manages database operations without requiring changes to the application's business logic or SQL statements. The application continues to use its existing code unchanged while the wrapper provides enhanced connection management, load balancing, and failover capabilities.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Ease of manufacture

If a management tool is not transparent to user or vendor applications, then management functions can be implemented, but compatibility and ease of use are reduced

Engineering Contradiction:

Improvemanagement function implementationVSAvoidapplication compatibility

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The data source wrapper is designed to be transparent to applications, meaning applications interact with the wrapper as if it were a standard data source without needing to know about or configure the advanced management features. The wrapper handles connection pooling, load balancing, and failover automatically in the background, making these management functions invisible to the application developer while maintaining full application compatibility.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS9015305B1Systems and methods for data source management

Publication Date: 2015.04.21 UNITED SERVICES AUTOMOBILE ASSOCIATION (USAA)

AI summary

Systems and methods for data source management using custom data sources are described. The system includes a custom data source created in response to a data source request, and a number of configuration modules to handle obtaining a connection with a data source. Other embodiments are also described.