Generic Database Gateway for Analytic Service Definition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database systems face challenges in allowing non-programmers to create and maintain database services due to proprietary programming languages, and they struggle to serve a diverse range of platforms efficiently, especially when standard communication platforms are not adapted for database services.
Innovation Solution
A generic database gateway server provides an interface to define and implement analytic database services by converting user inputs into objects that can be processed on database servers, using a non-proprietary protocol like OData, allowing designers to customize services without extensive coding and enabling consumption across various platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If proprietary programming languages are used to implement database services, then database services can be provided with complex functionality, but non-programmers find it difficult to generate and maintain these services
Solution Approach 1:
The patent introduces a service definition language (SDL) as an intermediary between users and the proprietary database system. The SDL provides a simplified, platform-independent interface that translates user-friendly service definitions into the complex proprietary language automatically, eliminating the need for users to learn complex programming languages while maintaining full database service functionality
Solution Approach 2:
The patent creates abstract service templates and metadata models that serve as reusable copies of common database service patterns. These templates encapsulate complex proprietary language constructs, allowing users to instantiate services by filling in simple parameters rather than writing complex code from scratch, thereby reducing maintenance burden while preserving functionality
2Adaptability or versatility
If standard communication platforms are used to access database services, then accessibility across diverse platforms is improved, but proprietary programming languages cannot be directly requested by these platforms
Solution Approach 1:
The SDL acts as a mediator layer between standard communication platforms and the proprietary database system. It translates standard platform requests into proprietary language commands and returns results in standard formats, enabling platform independence without requiring changes to the underlying proprietary database system or the client platforms
Solution Approach 2:
The service definition language is designed as a universal interface that can serve multiple different communication platforms simultaneously. By defining services in platform-independent SDL rather than platform-specific languages, the system achieves multi-functionality where a single service definition can be accessed by various platforms through standard protocols, reducing implementation complexity
Data Source
AI summary
An example database system comprises one or more database servers configured to serve database data of a database and configured to provide database services and a generic database gateway server coupled to the one or more database servers, the generic database gateway server configured to provide an interface to define analytic database services which can be called during run-time by inputting a uniform resource identifier at a user device to provide to the user device with database server data processed by one or more predefined analytic operations, the generic database gateway server being configured to obtain, during design time, a specification of an analytic database service by selecting database server data of the one or more database servers and one or more analytic operations to be applied on the selected data by the analytic database service, convert the obtained specification of the analytic database service into one or more objects in a format that can be processed on the one or more database servers, wherein the one or more objects include one or more analytic database service data objects specifying one or more attributes of the analytic database service and one or more analytic database service metadata objects, the one or more analytic database service metadata objects including annotations to the attributes of the one or more analytic database service data objects to be processed by the one or more database servers to implement the one or more predefined analytic operations and provide the one or more converted objects to the one or more database servers to be called by a user by inputting a uniform resource identifier.


