Declarative Driver Framework for Cloud Data Source Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems and methods for building drivers fail to provide a short turnaround time, do not use descriptive artifacts, lack protocol neutrality, and are not extensible or pluggable for custom use cases, especially when accessing various cloud data sources.
Innovation Solution
A system and method that utilize a declarative driver framework to obtain an interface description, mapping rules, and a protocol adapter, enabling rapid building of drivers for cloud data sources by generating descriptive artifacts and allowing protocol-neutral access and interaction, with features like schema descriptions, service identification rules, and data mapping rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a driver is built for each data source using existing systems, then data source access capability is provided, but development time and complexity increase significantly
Solution Approach 1:
The patent creates a universal driver framework that can access multiple different data sources through a common interface. The system defines standardized interface descriptions and mapping rules that work across various data sources, eliminating the need to build separate drivers for each source. This multi-functional approach allows a single driver framework to handle diverse data sources uniformly.
Solution Approach 2:
The patent segments the driver building process into distinct components: interface descriptions, mapping rules, and protocol adapters. This segmentation allows each component to be developed and configured independently, reducing overall complexity. The interface description separates data source metadata from access logic, while mapping rules separate query translation from execution, enabling modular development.
2Loss of time
If custom drivers are built for each cloud data source, then data source specific functionality is achieved, but turnaround time from research to delivery increases
Solution Approach 1:
The patent performs preliminary actions by pre-defining interface descriptions and mapping rules for common data sources. These templates contain pre-configured metadata schemas, query mapping patterns, and protocol adaptations. When a new data source is needed, the system can quickly instantiate a driver by selecting and customizing the appropriate template, dramatically reducing development turnaround time while maintaining adaptability through configurable parameters.
Solution Approach 2:
The patent enables rapid driver adaptation through parameter changes rather than code modifications. The interface descriptions and mapping rules contain configurable parameters that can be adjusted to match specific data source characteristics. This allows the same driver framework to adapt to different cloud data sources by changing configuration parameters, maintaining versatility while accelerating deployment.
3Adaptability or versatility
If protocol-specific drivers are implemented, then protocol-specific optimizations are achieved, but protocol neutrality and pluggability are lost
Solution Approach 1:
The patent introduces protocol adapters as intermediary components that sit between the universal driver framework and protocol-specific data sources. These adapters translate protocol-specific operations into the standardized interface described by the framework. This intermediary layer maintains protocol neutrality in the core system while preserving protocol-specific optimizations through specialized adapter implementations that can be plugged in as needed.
Solution Approach 2:
The patent creates a dynamic driver architecture where protocol adapters can be selectively activated based on the target data source. The system dynamically selects and configures appropriate protocol adapters at runtime, allowing the driver to adapt its behavior to match the specific protocol requirements of each data source while maintaining a unified interface. This dynamic adaptation preserves both protocol neutrality and protocol-specific performance.
Data Source
AI summary
A system and method for building a driver are disclosed. In one embodiment, the system includes one or more processors and a memory storing instructions that, when executed by the processor, cause the system to: obtain an interface description; obtain at least one mapping rule; operate a flow controller that controls a flow of operations, the operations using one or more of the interface description and the at least one mapping rule; obtain a protocol adapter; and implement access to a data source based on the operation of the flow controller using the obtained protocol adapter.