Handling multiple kafka partitions with Websocket subscription for device telemetry events #12053
unmeshjoshi
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I was looking at ThingsBoard Microservices / clustering architecture and see when Kafka is used for device telemetry/timeseries data, how Websocket subscriptions are handled at scale. From the initial look at the code and documentation, it looks like all the device events are channeled to a queue (e.g. Kafka) with fixed 10 partitions (as per the configuration) which all the core servers listen to. So all the core servers are identical in a way and will listen to all the 10 partitions. That allows handling Websocket subscriptions on any of the core node, without worrying about how to map Websocket clients to partitions etc. Is this understanding correct?
Beta Was this translation helpful? Give feedback.
All reactions