Database-less Leasing for Singleton Service Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing enterprise software applications relying on application servers struggle with high availability requirements for singleton services, particularly in scenarios where a High Availability (HA) database is not feasible, necessitating a database-less leasing system for efficient service migration and management.
Innovation Solution
A database-less leasing system is implemented within a cluster of application servers, where a cluster leader is determined and uses a lease table to manage singleton services, allowing for automatic migration and failover without relying on an external HA database. This system maintains copies of the lease table across servers, enabling seamless service migration and heartbeat mechanisms to ensure continuous operation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a High Availability database is used to manage leases for singleton services, then reliability and failover capability are improved, but device complexity and external dependency increase
Solution Approach 1:
The patent extracts the lease management functionality from the external High Availability database and relocates it to the application servers themselves. Each application server maintains local copies of the lease table, eliminating the single point of failure and reducing external dependency while maintaining failover capability through distributed local storage and heartbeat-based lease renewal mechanisms.
2Reliability
If a High Availability database is used for lease management, then availability is improved, but loss of time due to database operations and network latency increases
Solution Approach 1:
The centralized lease management system is segmented into distributed local lease tables on each application server. This eliminates the need for continuous database operations and network round-trips for lease checks, as each server can independently manage its local lease information and determine service ownership without external database queries.
3Stability of the object's composition
If lease tables are maintained centrally in a database, then consistency is improved, but device complexity and external dependency increase
Solution Approach 1:
The system implements heartbeat-based feedback mechanisms where application servers periodically renew their leases by sending heartbeat signals. The lease table on each server is updated based on this feedback, allowing local consistency to be maintained through distributed feedback loops rather than centralized database transactions.
Data Source
AI summary
One embodiment of the present invention comprises determining a cluster leader and using the cluster leader to set up a lease table at an application server of a cluster of application servers. The lease table can be used to maintain at least one lease for a singleton service.