Database Restoration Granularity Visualization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Databases are challenging to distribute while maintaining ACID properties, leading to costly and complex deployment and maintenance in existing 'shared nothing' and 'shared disk' models, which are not scalable or efficient for many use cases.
Innovation Solution
A distributed database system is implemented with a separate distributed storage service that offloads backup, restore, snapshot, and recovery operations from the database engine to the storage layer, allowing for asynchronous and lazy redo log processing across multiple nodes, reducing network traffic and improving scalability and availability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If databases are distributed using 'shared nothing' or 'shared disk' models, then fault tolerance and durability are improved, but deployment cost and system complexity increase significantly
Solution Approach 1:
The patent segments the database system into independent compute nodes that can be distributed across multiple machines. Each node handles a portion of the database workload independently, enabling fault tolerance through replication while maintaining manageable complexity at each node through modular architecture
Solution Approach 2:
The patent creates a universal distributed database architecture that can serve multiple use cases and workloads through a common platform. The system provides multi-functional capabilities including transaction processing, analytics, and backup operations through integrated services, reducing the need for separate specialized systems
2Adaptability or versatility
If monolithic database systems are replicated on multiple nodes with glue logic, then distribution is achieved, but cost and maintenance complexity increase
Solution Approach 1:
The patent extracts the database management functionality from monolithic replicated systems and implements it as coordinated distributed services. The glue logic is replaced by a coordinated approach where a master node manages metadata and coordination while worker nodes execute operations, eliminating the need for complex custom integration code
Solution Approach 2:
The patent introduces a master node as an intermediary that coordinates operations between worker nodes. This mediator handles metadata management, query routing, and transaction coordination, simplifying the distribution architecture by centralizing control functions while maintaining distributed execution
3Reliability
If backup and restore operations are performed on the database engine, then data protection is achieved, but network and I/O bandwidth requirements increase
Solution Approach 1:
The patent extracts backup and restore operations from the database engine and implements them as storage-layer operations. Backup data is written directly to object storage by the storage service without requiring extensive network transfer through the database engine, reducing network and I/O bandwidth requirements
Solution Approach 2:
The storage service performs backup operations autonomously by directly writing data to object storage without requiring active participation from the database engine. The system enables self-service backup where the storage layer independently manages data protection operations
Data Source
AI summary
A database may provide a visualization of restoration operation granularity. Information may be obtained describing possible restoration points within a given period of time for a database. The information may include a respective state of the database associated with a point in time and a respective restoration operation type for the possible restoration points. A graphical representation may be generated illustrating the possible restoration points ordered within the given time period according to the points in time associated with the respective states of the database. The graphical representation may be provided via network-based interface to a client of the database. The graphical representation of the possible restoration points may be updated in response to changes to the given time period or database volume events that modify the possible restoration points.