@Serverless Land It was said each user id is used to subscribe to users own topic , so which component creates this topic after user is logged in ? this dynamic topic should be created and destroyed so that thousands of topics are not kept after being used . this is an amazing idea by the way need some more insights into this
The subscription is made by the front end appliction upon login, Once the session is closed (browser shut) the subscription ends. this is all handled by IoT core.
@@ServerlessLand Thanks . so subscription will end with browser but the dedicated user topics would be created when users are created right ? so each user has a topic living as long as user is in the system ? any training videos you can point to for this subject
@Serverless Land It was said each user id is used to subscribe to users own topic , so which component creates this topic after user is logged in ? this dynamic topic should be created and destroyed so that thousands of topics are not kept after being used . this is an amazing idea by the way need some more insights into this
The subscription is made by the front end appliction upon login, Once the session is closed (browser shut) the subscription ends. this is all handled by IoT core.
@@ServerlessLand Thanks . so subscription will end with browser but the dedicated user topics would be created when users are created right ? so each user has a topic living as long as user is in the system ?
any training videos you can point to for this subject
Thanks. Why using MQTT (IoT core meeant to be for IoT...), when it could be used directly WebSockets for web applications?
Using IoT core in this way allows us to fan out to multiple connections (devices) without having to create and manage additional endpoints.
0