Runtime Metadata for Vendor-Specific DaaS Dataset Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing DAAS systems require recompilation and redistribution of software for any updates to vendor-specific configuration information, making the process inefficient.
Innovation Solution
Utilize ingestion/search metadata and match metadata to configure ingestion, analysis, indexing, and querying services during runtime, allowing adjustments without recompilation and redistribution of the DAAS system software.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If vendor-specific configuration information is updated using traditional methods, then the DAAS system can be reconfigured, but recompilation and redistribution of software is required which reduces efficiency
Solution Approach 1:
The patent segments the DAAS system into distinct modules: a runtime engine that executes operations and a separate metadata repository that stores configuration information. This segmentation allows configuration updates to occur independently without requiring full system recompilation, thereby improving reconfiguration efficiency while maintaining adaptability.
Solution Approach 2:
The patent implements dynamic configuration by allowing vendor-specific configuration information to be updated in the metadata repository at runtime. The runtime engine can retrieve and apply these updates without system recompilation, making the system both adaptable to changes and efficient in applying those changes.
2Adaptability or versatility
If vendor-specific configuration information is updated frequently, then the system can adapt to new requirements, but the cost and time of recompilation and redistribution increases
Solution Approach 1:
The patent performs preliminary actions by pre-compiling the runtime engine with the capability to dynamically load and execute configuration instructions from metadata. This preliminary preparation eliminates the need for recompilation during subsequent configuration updates, reducing both time and cost while maintaining adaptability.
Solution Approach 2:
The patent uses metadata as a copyable representation of configuration information that can be updated and distributed independently of the main system binary. Changes are propagated by updating the metadata copy rather than redistributing the entire system, significantly reducing update time and cost.
3Manufacturing precision
If the DAAS system is recompiled for configuration updates, then configuration accuracy can be ensured, but the process becomes less cost-effective
Solution Approach 1:
The patent introduces metadata as an intermediary layer between the configuration requirements and the runtime engine. This intermediary allows configuration information to be updated and validated separately, ensuring accuracy through metadata validation rules while avoiding the high costs of full system recompilation and redistribution.
Data Source
AI summary
A method for configuring the operation of the software of a data as a service (DAAS) system during run time is described. The configuring includes receiving a match query from a customer relationship management system that transmitted the match query responsive to a user using an interface to trigger an update of records in the customer relationship management system that were previously imported from the DAAS system, querying for records in the dataset that match records in the customer relationship management system previously imported from the DAAS system, the querying configured at run time according to metadata that identifies, for records in the dataset, a field to match on and a match threshold, and producing a match query result that includes records in the dataset to be imported to update records that were previously imported from the DAAS system.