Automated Customization Preservation in Data Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data management systems face challenges in preserving customizations across software release updates, particularly for companies with customized data warehouses and ETL pipelines, as manual processes are inefficient and cannot scale for large numbers of customers with disparate customizations.
Innovation Solution
An automated code-driven approach using stored metadata to support customizations, including generating executable code based on metadata that describes data schemas, ETL processes, and reporting functionality, allowing for efficient and scalable preservation of customer-specific customizations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual processes are used to preserve customizations across software updates, then customization preservation can be achieved for individual customers, but the process becomes inefficient and cannot scale for large numbers of customers with disparate customizations
Solution Approach 1:
The patent replaces manual mechanical processes with an automated code-driven system. A customization preservation module automatically detects customizations by comparing customer-specific code against base image code, generates executable code to preserve customizations, and applies them across software updates without human intervention, thereby scaling efficiently to numerous customers.
Solution Approach 2:
The system enables self-service automation where the customization preservation module autonomously identifies, preserves, and applies customizations. The module compares code versions, determines customization differences, generates preservation code, and executes updates automatically, eliminating the need for manual intervention while handling multiple customers simultaneously.
2Adaptability or versatility
If code-driven automated approach is implemented, then scalability and efficiency improve for handling multiple customers, but system complexity increases due to metadata management and code generation mechanisms
Solution Approach 1:
The patent introduces a customization preservation module as an intermediary between the base software image and customer-specific customizations. This module manages metadata, compares code versions, generates preservation code, and coordinates the application of customizations, thereby simplifying the overall system architecture while enabling scalable automated customization preservation across multiple customers.
Data Source
AI summary
Approaches for preserving customizations made to a data management system. Metadata that identifies a mapping between data fields of one or more data source schemas to columns of one or more data tier schemas is maintained. Each of the one or more data tier schemas stores data retrieved from the one or more data source schemas. Values from the metadata are read to dynamically generate software processes. The software processes may update one or more existing ETL processes to reflect an updated state of the one or more data tier schemas and may generate any new ETL processes required to retrieve data stored in the one or more data source schemas and load the retrieved data into the one or more data tier schemas. Customizations made to portions the data management system are preserved in an automated fashion when new versions of system components are deployed.