API Schema Proxy Objects for Database Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Consumers face challenges in reliably accessing database objects managed by applications due to mutable implementation details, lack of well-defined access interfaces, and security restrictions, leading to interoperability issues and restricted database-level access.
Innovation Solution
The implementation of API schemas with database-level proxy objects that provide access to database objects independently of the application, using API objects as proxies to manage access rights and enforce modification constraints through API contracts, allowing consumers to access database objects without relying on the application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If database-level access is provided to database objects, then accessibility and interoperability are improved, but reliability and security are worsened due to mutable implementation details and lack of well-defined access interfaces
Solution Approach 1:
The patent introduces an API schema as an intermediary layer between consumers and database objects. This API schema includes API objects that serve as stable, well-defined interfaces, mediating all access to the underlying database objects. The API schema acts as a contract that remains stable even when implementation details change, thereby maintaining reliability while enabling broad accessibility.
Solution Approach 2:
The patent segments the access interface from the database object implementation. The API schema is separated into distinct API objects that represent stable interfaces, while the underlying database objects can evolve independently. This segmentation allows the interface layer to remain stable and reliable while the implementation layer can be modified for versatility.
2Reliability
If application-based access control is used, then security is improved, but ease of operation and flexibility are worsened due to restricted database-level access
Solution Approach 1:
The API schema serves as an intermediary that enables fine-grained access control. Instead of relying solely on application-based security, the API schema objects themselves can be granted or revoked to consumers, providing a more direct and flexible mechanism for controlling access while maintaining security.
Solution Approach 2:
The patent enables dynamic access control where API objects can be selectively granted or revoked from consumers based on needs. This dynamic mechanism allows security to be maintained while providing flexibility and ease of operation, as access rights can be adjusted without changing the underlying application structure.
3Reliability
If API schemas with proxy objects are implemented, then reliability and access control are improved, but device complexity and configuration requirements are worsened
Solution Approach 1:
The patent creates API objects as copies or representations of database objects within the API schema. These API objects serve as stable proxies that mirror the structure and interface of the underlying database objects without exposing the complexity of the implementation. Consumers interact with the simplified API objects rather than the complex database objects directly.
4Reliability
If direct database access is prohibited, then security and integrity are improved, but productivity and access efficiency are worsened
Solution Approach 1:
The API schema provides a direct database access path through its API objects, eliminating the need to route all access through the application layer. This intermediary layer maintains integrity by providing controlled access paths while improving productivity by enabling efficient database operations without application overhead.
Data Source
AI summary
Disclosed herein are system, method, and device embodiments for consuming application-owned database objects via an API schema. An embodiment operates by determining that an application-owned database object is classified as API exposable, creating an API schema for proxy access to database objects that have been identified as API exposable, generating an API object within the API schema based on assigning the database object to the API schema, and providing, via the API schema and independent of the application, access to the API object by a privileged consumer.