You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 11, 2024. It is now read-only.
Current application exposes a websocket server that broadcasts message validation errors.
It is done using Go channels, meaning only validation errors that happened in that particular machine will be broadcasted later.
The issue comes whenever you have more than one instance of the app running (e.g. behind a LB).
Example: The client connects to the websocket server of machine A, but the message validation error happens on machine B.
Add an option to publish validation errors to another queue (Kafka topic in this first implementation) so it can be consumed by all instances at the same time.
The text was updated successfully, but these errors were encountered:
smoya
changed the title
Websocket server should consume from a queue so all instances broadcast the same
Websocket server should consume from a queue so all instances broadcast the same events
Sep 10, 2021
Current application exposes a websocket server that broadcasts message validation errors.
It is done using Go channels, meaning only validation errors that happened in that particular machine will be broadcasted later.
The issue comes whenever you have more than one instance of the app running (e.g. behind a LB).
Example: The client connects to the websocket server of machine A, but the message validation error happens on machine B.
Add an option to publish validation errors to another queue (Kafka topic in this first implementation) so it can be consumed by all instances at the same time.
The text was updated successfully, but these errors were encountered: