Singleton Micro-Service High Availability Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current micro-service architectures face challenges in achieving high availability for singleton micro-services, particularly in milliseconds to seconds, due to the lack of active/passive POD configurations provided by cloud providers.
Innovation Solution
A method is proposed to enhance high availability in pod-based cloud deployment architectures by using an internal controller to identify pod/container failures, initiate label changes for standby pods, and redirect traffic to ensure continuous service availability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a singleton micro-service uses a single active POD without standby configurations, then device complexity is reduced and ease of operation is improved, but reliability deteriorates because if the container/task in that POD fails, it disrupts the high availability of the complete product
Solution Approach 1:
The system pre-configures standby PODs alongside the active POD before any failure occurs. These standby PODs are ready to immediately take over when the active POD fails, eliminating the need for complex runtime configuration decisions and ensuring high availability through advance preparation
Solution Approach 2:
The service label mechanism acts as an intermediary that automatically routes traffic between active and standby PODs. When a POD fails, the label change redirects traffic to the standby POD without requiring complex manual intervention or system reconfiguration
2Reliability
If cloud providers do not provide active/passive POD configurations, then ease of manufacture is improved and device complexity is reduced, but reliability worsens because singleton micro-services cannot achieve rapid failover
Solution Approach 1:
The system implements self-service failover through automated label management. When a POD fails, the system automatically detects the failure, changes the service label to point to the standby POD, and restores service continuity without requiring external cloud provider features or complex manual configuration
Solution Approach 2:
The system changes the service label parameter to redirect traffic from the failed POD to the standby POD. This simple parameter change enables rapid failover and restores high availability without requiring complex manufacturing or deployment processes
Data Source
AI summary
A method is disclosed for providing singleton micro-service high availability, comprising: identifying, by an internal controller, that a pod/container has crashed; initiating, by the internal controller, a label change for an existing similar pod labeled as standby to active; matching a singleton micro-service selector label criterion; advertising the newly re-labeled existing similar pod as part of a singleton micro-service; and receiving, by the newly relabeled pod in the system, traffic directed on an IP address of the singleton micro-service.