HTTP Sticky
Handpick the service of your choosing
README.md
Responses:
HTTPS
WSS
page_by:
app-1
client_id:
dmr
Ws_connection:
Enter your message
HTTP & Round Robin
i
Requests are serially delivered to application containers in round robin fashion.
HTTP & Sticky
i
Sticky cookie added by app instance ensures that all future requests reach the same instance every time.
This includes the initial ws connection request.
WebSockets Only
i
WS connections are long lived. After connection is made, all messages are delivered to the same app instance.
This is true regardless of the usage of sticky headers.
Publish Message to Queue
i
Standard method of handling WS connections.
Messages are published to queue and the container with the recipient's connection does the delivery.
non-sticky HTTP & in-memory WebSockets
i
WS response NOT GUARANTEED.
No sticky cookie in http request. App instance that has the client's websocket session may not receive it.
sticky HTTP & in-memory WebSockets
i
Uses sticky cookie-based routing for http.
WebSocket connections carry the same cookie, and are routed to same instance.