Reactive API Gateway for Multi-Channel Session Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing service platforms face challenges in tightly integrating multiple services, leading to fragmented interactions between client applications and service subsystems, which complicates the management of API calls and event messages across multiple user agents and channels.
Innovation Solution
A reactive API gateway is implemented to manage connections between user agents and service subsystems, routing API calls and pushing event messages to appropriate channels, thereby centralizing interactions and maintaining session state consistency across multiple channels in real-time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If services are developed independently over extended period, then service development flexibility is improved, but service integration complexity increases
Solution Approach 1:
The patent introduces an API gateway as an intermediary component that sits between client applications and service subsystems. The gateway manages API calls, routes requests to appropriate services, and handles event messages, thereby mediating the interactions between independently developed services and reducing integration complexity.
Solution Approach 2:
The API gateway performs multiple functions including routing API calls to service subsystems, managing user sessions across multiple channels, pushing event messages to appropriate user agents, and maintaining connection state. This multi-functional approach consolidates integration logic in a single component.
2Reliability
If API gateway pushes events to all connected channels, then user experience consistency is improved, but network traffic increases
Solution Approach 1:
The patent implements selective event pushing where the API gateway determines which user agents should receive specific event messages based on their connection state and relevance. Not all connected channels receive all events, allowing optimization of network traffic while maintaining consistency for relevant users.
Data Source
AI summary
A system for processing application programming interface (API) calls and event messages may include a gateway subsystem and an events hub. The gateway subsystem can route API calls submitted by user agents connected to the gateway subsystem to appropriate service subsystems. The events hub can receive event messages from at least some of the service subsystems and publish the received event messages for consumption by one or more consuming subsystems including the gateway subsystem. A first published event message may specify a first user and the gateway subsystem can (i) determine every user agent that is associated with the first user and that is currently connected to the gateway subsystem and (ii) transmit information that represents the first published event message to every user agent that is determined to be associated with the first user and currently connected to the gateway subsystem.