Centralized ID Range Allocator for Stateful Application Stickiness
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Stateful applications in cloud infrastructure face limitations due to stickiness, which hampers high availability, scalability, and software upgrades, as sessions and transactions are tied to specific instances, restricting the utilization of cloud features.
Innovation Solution
A Centralized ID Range Allocator and in-memory database enable session and transaction reassignment across application instances, breaking stickiness through internal function discovery and efficient ID management, ensuring high availability and scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If stateful applications use stickiness to maintain session state, then session consistency is improved, but scalability and high availability deteriorate
Solution Approach 1:
The patent segments the session state management by introducing a separate session management component that handles state persistence independently from the application instances. This allows application pods to be stateless while session state is maintained in a centralized store, enabling scalability without sacrificing session consistency.
Solution Approach 2:
The patent introduces an intermediary session management layer that mediates between application instances and session state. This intermediary handles session persistence and retrieval, allowing multiple application instances to access the same session state without direct coupling, thus improving both scalability and session consistency.
2Reliability
If stateful applications use stickiness for transaction handling, then transaction integrity is improved, but cloud infrastructure utilization deteriorates
Solution Approach 1:
The patent extracts the stateful transaction management functionality from the application instances and places it in a dedicated session management component. This extraction allows application pods to remain stateless and fully utilize cloud infrastructure features like load balancing and auto-scaling, while transaction integrity is maintained through the centralized session management layer.
Solution Approach 2:
The session management component serves multiple functions: maintaining session state, ensuring transaction integrity, and supporting multiple application instances simultaneously. This multi-functionality reduces overall system complexity while improving cloud infrastructure utilization compared to having each application instance maintain its own state.
3Ease of operation
If stateful applications implement session stickiness, then session state management is simplified, but high availability and software upgrades are hindered
Solution Approach 1:
The patent implements session state copying where application instances retrieve session state from the centralized session management component as needed. This copying approach simplifies session state management for individual instances while the centralized store ensures high availability through redundancy and enables seamless software upgrades without session loss.
Data Source
AI summary
A method is disclosed, comprising: determining, at an application pod, Responsibility of allocation/deallocation of individual protocol identifier; receiving, at a centralized identifier Range allocator, a request from the application pod, the request including an address of the application pod; assigning, at the centralized identifier range allocator, a new range in response to the received request; sending, from the centralized identifier range allocator to a database, and responding, from the centralized identifier range allocator to the application pod, the new identifier range.