Database Event Notification Replication for Failover Availability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database management systems (DBMS) typically do not share event notification registrations with other DBMSs, resulting in loss of availability for clients who failover or migrate to standby systems due to DBMS failures.
Innovation Solution
Replicating event notification registrations to a designated secondary DBMS, ensuring that notifications are maintained and delivered even if the primary DBMS fails, through a replication process that includes storing original registrations in one database and replicating them to another via a communication link, with options for automatic replication based on client preferences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If event notification registrations are stored only in the primary DBMS, then the system structure is simple, but availability is lost during DBMS failures
Solution Approach 1:
The patent creates a copy of the event notification registrations from the primary DBMS to a secondary DBMS. This copying mechanism ensures that if the primary DBMS fails, the registrations are still available in the secondary DBMS, thereby improving reliability without significantly complicating the system structure
Solution Approach 2:
The patent performs preliminary replication of event notification registrations to a secondary DBMS before any failure occurs. This advance preparation ensures that when a failure happens, the registrations are already available in the secondary system, eliminating the need for complex real-time synchronization mechanisms
2Reliability
If event notification registrations are replicated to a secondary DBMS, then availability during failover is ensured, but system complexity increases
Solution Approach 1:
The patent implements a copying mechanism where event notification registrations are replicated from the primary DBMS to a secondary DBMS. This approach ensures continuous availability during failover while keeping the replication infrastructure relatively simple by using standard database copying techniques
Solution Approach 2:
The secondary DBMS is designed to serve multiple purposes: it can act as a standby system for failover, a test environment, or an additional production system. This multi-functionality reduces the need for dedicated backup infrastructure, thereby limiting the increase in system complexity
3Reliability
If all event notification registrations are replicated, then availability is maximized, but replication overhead and resource consumption increase
Solution Approach 1:
The patent allows different event notification registrations to have different replication preferences. Critical registrations can be replicated to ensure high availability, while less critical ones may not be replicated. This selective approach maximizes availability for important notifications while minimizing replication overhead
Solution Approach 2:
The patent introduces a replication preference parameter that can be set for each event notification registration. This parameter controls whether and how the registration is replicated, allowing the system to adjust replication behavior based on the criticality and resource constraints, thereby optimizing the balance between availability and overhead
Data Source
AI summary
A method of ensuring availability of event notification registrations of a database management system is described and provided. The method comprises creating the event notification registrations and storing the event notification registrations in a database of the database management system. Further, the event notification registrations are replicated in a designated database management system to create replicated event notification registrations. If the database management system fails, the replicated event notification registrations are utilized.