Identity Domain Snapshot Versioning for Zero-Downtime Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Inconsistencies in identity domains and tenancies within cloud computing systems lead to service disruptions, vulnerabilities, and inconsistent user experiences due to bugs or data corruption, necessitating updates that cause significant downtime.
Innovation Solution
The implementation of identity domain snapshotting using versioning and containerization, where an updated identity domain configuration is snapshotted and consumed, with metadata entries being purged, reducing downtime and optimizing the speed of the data objects are copied, and metadata are updated to reduce the metadata, and the system updates the active version of the identity domain from the current version to the updated version, ensuring seamless transitions and minimizing downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional updates are applied to fix inconsistencies in identity domains, then the bugs and data corruption issues are resolved, but significant downtime occurs and service availability is reduced
Solution Approach 1:
The system creates a snapshot of the identity domain before applying updates, allowing the update to be applied without taking the system offline. The snapshot preserves the previous state, enabling rapid rollback if needed, while the update process can proceed in parallel with continued service operation.
Solution Approach 2:
Instead of modifying the active identity domain in place, the system creates a copy (snapshot) of the domain state and applies updates to the copy. This allows the updated version to be prepared separately and then switched to active status without disrupting ongoing services, thus eliminating downtime.
2Reliability
If identity domain updates are applied to resolve inconsistencies, then data integrity is improved, but system performance and update speed are reduced
Solution Approach 1:
The system performs preliminary actions by creating a snapshot of the identity domain before updates are applied. This snapshot captures the complete state at a point in time, allowing subsequent updates to be applied efficiently without repeatedly scanning or processing the entire domain, thus improving update speed while maintaining data integrity.
Solution Approach 2:
By copying the identity domain into a snapshot, the system enables updates to be applied to the copy rather than the live system. This separation allows for faster update processing and easier comparison of changes, improving both data integrity verification and update speed.
3Reliability
If comprehensive metadata entries are maintained in the identity domain, then data completeness is improved, but system complexity and data management overhead increase
Solution Approach 1:
The system creates a snapshot copy of the identity domain that includes all metadata entries at a specific point in time. This snapshot can be stored and referenced without requiring continuous management or updates of the metadata structure itself, reducing operational complexity while preserving complete data information.
Solution Approach 2:
By capturing metadata entries in a preliminary snapshot action, the system preserves data completeness at the time of snapshotting without requiring ongoing complex management procedures. The snapshot serves as a static, complete record that simplifies future data management operations.
Data Source
AI summary
Techniques for identity domain snapshotting and snapshot consumption using versioning are disclosed. A snapshot of an updated identity domain is received and applied to an identity domain to change the active version of the identity domain from a prior current version to the updated version. The snapshot is consumed by loading data objects in a hierarchical manner into an updated identity domain. While data objects belonging to the snapshot are loaded during consumption of the snapshot, client traffic continues to be served by the prior, non-updated version of the identity domain. Once consumption of the snapshot is completed successfully, the updated version of the identity domain becomes the active version. The prior version is then recorded in a cleanup table denoting that cleanup operations shall be performed for entities related to the data objects and associated with the prior version.