Master-Slave Database Architecture for Address Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional DNS/ENUM routing systems face performance limitations due to the concurrent use of a single database by clients and provisioning tools, leading to reduced system performance and increased complexity.
Innovation Solution
A system comprising a master database and multiple slave databases, with transfer agents that read and write data from the master to the slave databases, allowing for load isolation, redundancy, and tailored data structures for different applications, enabling efficient query performance and improved security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single database is used for both provisioning operations and query operations, then system complexity is reduced, but system performance deteriorates due to concurrent access conflicts
Solution Approach 1:
The patent divides the single database into multiple separate databases: a master database for provisioning operations and multiple slave databases for query operations. This segmentation allows concurrent access without conflicts, as provisioning tools access only the master database while multiple clients simultaneously access different slave databases, thereby resolving the performance deterioration caused by concurrent access conflicts.
2Device complexity
If a single database is used for both provisioning and queries, then data consistency is simplified to maintain, but query performance deteriorates due to resource contention
Solution Approach 1:
By separating the database into master and slave databases, the patent enables parallel query processing across multiple slave databases while provisioning operations occur independently on the master database. This eliminates resource contention between provisioning and query operations, significantly improving query performance without complicating data management, as the master database serves as the single source of truth for data consistency.
3Reliability
If the master database handles all read operations, then data accuracy is maintained, but system scalability deteriorates
Solution Approach 1:
The patent segments read operations across multiple slave databases that are synchronized with the master database. Each slave database can independently handle query operations while maintaining data accuracy through synchronization with the master database. This architecture enables horizontal scaling by adding more slave databases to handle increased query loads without compromising data accuracy, thus improving system scalability.
Solution Approach 2:
The patent creates multiple copies of the database data in slave databases that are synchronized with the master database. These copies enable concurrent read operations without affecting the master database or each other, allowing the system to scale horizontally by adding more slave database copies to handle increased query demands while maintaining data accuracy through synchronization mechanisms.
4Productivity
If multiple slave databases are introduced, then query performance improves through load distribution, but system complexity increases
Solution Approach 1:
The patent segments the database architecture into a clear master-slave hierarchy where the master database handles provisioning and slave databases handle queries. This segmentation improves query processing capacity by distributing read loads across multiple slave databases while maintaining manageable system complexity through well-defined roles and access patterns, with provisioning tools accessing only the master database and clients accessing only slave databases.
Data Source
AI summary
A system for resolving addresses in an internet protocol based network. The system includes an address resolving master database and a plurality of slave databases. A plurality of transfer agents are each allocated to different ones of the plurality of slave databases for reading data from the master database and writing it to the slave databases. Each slave database receives and stores either ENUM data or DNS data, but not both. A plurality of applications have read access to at least one of the plurality of slave databases.