Copy Data Tokens for Version Control Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for obtaining copies of production data face challenges such as performance drops, data integrity concerns, and lengthy restoration times, especially when dealing with complex and large datasets, and there is a need for a solution that allows secure, efficient, and scalable access to transformed data across different environments.
Innovation Solution
The implementation of copy data tokens, which are self-describing entities that facilitate the management and sharing of data through a computerized method integrating data tokens into version control systems, enabling automatic management of copy data and providing secure, controlled access without impacting production data integrity or performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a simple copy of production data is created, then data access is provided to external groups, but performance drop occurs and data integrity is compromised
Solution Approach 1:
The patent uses snapshot technology to create virtual copies of production data that can be accessed by external groups without affecting the original data. These snapshots are read-only copies that maintain data integrity while enabling widespread access for development, testing, and analytics purposes.
Solution Approach 2:
The patent introduces a data virtualization layer that acts as an intermediary between production data and external users. This layer provides controlled access through snapshots and copy data tokens, preventing direct access to production data while still enabling necessary data consumption for various purposes.
2Reliability
If data is copied from backup, then independent copy is obtained that does not affect production data, but restoration time increases to hours or days
Solution Approach 1:
The patent implements continuous snapshotting of production data, creating pre-prepared copies that are ready for immediate use. Instead of restoring from backup when needed, snapshots are continuously maintained in advance, reducing retrieval time from hours/days to seconds while maintaining data independence.
Solution Approach 2:
The patent changes the temporal parameter of data availability by implementing real-time or near-real-time snapshotting. This transforms the data copy process from periodic (daily backups) to continuous, enabling rapid access to historical data states without the delays associated with traditional backup restoration.
3Productivity
If copy data virtualization is implemented, then independent copies are provided quickly, but system complexity increases
Solution Approach 1:
The patent creates a universal snapshot management system that handles multiple data types, storage locations, and access scenarios through a single platform. The copy data token mechanism provides a unified interface for creating, managing, and accessing data copies across different environments (development, testing, analytics) without requiring separate systems for each use case.
Solution Approach 2:
The patent implements automated snapshot management where the system automatically creates, maintains, and manages data copies without requiring manual intervention. Copy data tokens enable self-service access where users can independently obtain and manage their own data copies, reducing the operational burden on IT staff while maintaining rapid copy creation capabilities.
4Ease of operation
If production data is copied to development and test environments, then data access is enabled, but security protections are lost
Solution Approach 1:
The patent creates read-only snapshot copies of production data that can be freely distributed to development and test environments. These snapshots maintain the exact data state but cannot be modified, eliminating security risks associated with data manipulation while preserving full data access for testing and development purposes.
Data Source
AI summary
Computerized systems and methods are provided for integrating copy data tokens with source code repositories. A first command associated with the version control system stores in the memory a copy of source code and a copy of the data token from the remote repository, comprising source data and mount data. A second command associated with the version control system is executed to create a version of the source code stored in the memory. Based on the execution of the second command a working copy of the copy data is created based on the data token for use with the version of the source code, comprising creating a copy of the copy data from the data source based on the source data, and mounting the working copy to the device based on the mount data, thereby automatically managing the copy data for the version control system.