Session Failover via Asynchronous Bus Mechanism

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing session failover mechanisms suffer from performance degradation and lack scalability due to increased network latency and memory consumption when replicating session information across multiple servers and databases, leading to bottlenecks and inefficiencies in storing and retrieving session data.

Innovation Solution

An asynchronous interaction model is introduced where session information is stored through a bus mechanism, allowing session servers to operate independently of databases, reducing direct connections and enabling faster data retrieval and storage without the need for servers to interact with or be aware of individual databases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If session information is replicated across multiple servers and databases to ensure failover capability, then reliability is improved, but network latency and memory consumption increase

Engineering Contradiction:

Improvefailover capabilityVSAvoidnetwork latency

Core Design Contradiction:

ReliabilityVSSpeed

Solution Approach 1:

The patent introduces a bus mechanism as an intermediary layer between session servers and databases. The bus mechanism manages session information replication and retrieval asynchronously, eliminating direct server-database connections and reducing network latency while maintaining failover capability across multiple servers and databases.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by asynchronously replicating session information to multiple databases in advance. This ensures that when a failover event occurs, the necessary session data is already available at backup locations, eliminating the need for synchronous data retrieval and reducing latency during critical failover moments.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If session servers directly connect to multiple databases for session storage, then reliability is improved, but device complexity and scalability deteriorate

Engineering Contradiction:

Improvesession data availabilityVSAvoidserver-database connections

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The bus mechanism serves as a central intermediary that manages all interactions between session servers and databases. Servers communicate with the bus mechanism rather than directly connecting to databases, significantly reducing the complexity of server-database connections while maintaining reliable session data availability through the bus's coordinated access to multiple databases.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The bus mechanism provides universal access to multiple databases for session information storage and retrieval. Instead of each server maintaining direct connections to specific databases, the bus mechanism universally interfaces with all databases in the system, enabling any server to access session data through the bus without establishing complex direct connections to individual databases.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Stability of the object's composition

If synchronous database acknowledgments are required for session storage, then data consistency is improved, but productivity and recovery speed deteriorate

Engineering Contradiction:

Improvedata consistencyVSAvoidrecovery speed

Core Design Contradiction:

Stability of the object's compositionVSProductivity

Solution Approach 1:

The system performs preliminary asynchronous replication of session information to multiple databases before operations complete. This preliminary action ensures data consistency is maintained through eventual consistency models while dramatically improving recovery speed, as the system can immediately retrieve replicated data without waiting for synchronous acknowledgments during failover events.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The bus mechanism implements beforehand cushioning by asynchronously replicating session data to multiple databases in advance of any failure event. This prior cushioning ensures that when a server fails, the replicated data is already available at backup locations, eliminating the need for synchronous acknowledgments and maximizing recovery speed while maintaining data consistency through the replicated copies.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS8051179B2Distributed session failover

Publication Date: 2011.11.01 ORACLE AMERICAN INC

AI summary

A distributed session failover mechanism is disclosed for facilitating the replication and retrieval of session information. A first server, in a trusted network, providing a single sign-on (SSO) solution, stores session information pertaining to a particular client requesting services associated with the server. In order to provide session failover, the first server sends a copy of the session information to a bus mechanism, which is connected to one or more persistent repositories. When a second server attempts to validate the client, the second server may discover that the first server failed. The second server then requests a copy of the session information pertaining to the client from the bus mechanism. The bus mechanism retrieves the copy from a persistent repository and provides the copy to the second server.