Dynamic OData Service Generation for Legacy Database Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex enterprise applications, particularly those relying on legacy database systems, face challenges in adapting to remote access and cloud-based services due to impracticality of updating database management systems, leading to difficulties in dynamically providing access to new data services without restarting servers.
Innovation Solution
The solution involves dynamically creating and registering web services, such as OData services, during application runtime using a service generator that converts physical database artefacts into virtual data models, allowing new data services to be added or modified without restarting the server, by utilizing a service map for routing requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If legacy database management systems are used, then system stability and existing functionality are maintained, but adaptability to cloud-based remote access is limited
Solution Approach 1:
The patent introduces a service generator as an intermediary component that sits between the legacy database management system and the cloud-based access layer. This service generator dynamically creates web services (OData, REST) that expose database functionality through standard web protocols, allowing cloud-based remote access without modifying the underlying legacy database system. The intermediary translates modern web service requests into legacy database operations, resolving the contradiction between maintaining legacy system stability and enabling cloud adaptability.
2Productivity
If web services are dynamically created during runtime, then service updates and new data artefacts are immediately available, but server restart requirements are eliminated
Solution Approach 1:
The patent implements dynamic service creation where the service generator continuously monitors the database schema and automatically generates updated web services when data artefacts change. The service registry maintains a live mapping between database objects and their corresponding web service endpoints, allowing runtime updates without server restart. This dynamic approach enables immediate service deployment while managing complexity through automated service generation and registration mechanisms.
Solution Approach 2:
The system implements a feedback loop where the service generator monitors database schema changes, triggers service regeneration, and updates the service registry automatically. When the database schema changes, the system detects this change, regenerates the appropriate web services, and reregisters them with the routing table, creating a self-updating service layer that responds to database changes in real-time without requiring manual intervention or server restart.
3Ease of operation
If automated service generation is implemented, then technical expertise requirements are reduced, but automation extent increases
Solution Approach 1:
The service generator operates as a self-service system that automatically monitors database schema changes and generates corresponding web services without requiring manual programming or technical expertise. The system reads database metadata, understands the data model structure, and autonomously creates appropriate OData or REST service definitions, registers them with the routing table, and makes them immediately available for cloud access. This self-service capability dramatically reduces the technical expertise required while managing automation complexity through standardized service generation templates.
Data Source
AI summary
Techniques and solutions are described for providing access to data using web services, such as OData services. OData services can be dynamically added to a routing table used by a router. The router can be statically registered with an application instance, such as a server associated with the application instance. A web service can be generated from a definition of a data artefact, such as a table or view, stored in a database. A virtual data artefact corresponding to the data artefact can be generated, and used to generate the web service. A message service can cause web services to be generated when a data artefact is added or changed.