Abstract

A two-stage connection-upgrade mechanism is provided for controller-agent architectures. An agent first establishes an authenticated control connection through an application programming interface (API) gateway, which routes the connection to an agent-server instance. The server creates a session key, selects a suitable server node, and instructs the agent to reconnect directly using the selected node's Internet Protocol (IP) address, port, session key, and configuration parameters. After validating the session key, the selected server establishes a direct data connection that bypasses the API gateway and intermediate cluster hops. The mechanism retains gateway-based authentication and load distribution while supporting higher throughput, lower latency, increased scale, reduced tromboning, and improved resilience. The first connection can be retained for failover or closed after the direct connection is stable.

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.

Share

COinS