Hello!
I believe one of the key aspect of the IoT
Server will be the “blackbox event hub” mentioned in the
https://wiki.eclipse.org/IoT/IoTServerPlatform
– that is, the ability for consumers to subscribe to
events/feeds. From a scalability and bandwidth perspective,
this could however become tricky with lots of subscribers. A
single event could end up generating tons of messages
distributed across to all subscribers.
One way to work around the bandwidth issue
could be that all consumers need to be ‘local’ to an IoT
Server. The subscription could then happen between IoT servers
(on behalf of the final subscriber), thus minimizing the need
for bandwidth, as an event would be propagated just once
between all (subscribed) IoT servers, and then to the ‘local’
devices.
On the other hand, having multiple IoT
Servers also implies multiple feed “repositories”. By making
the servers participate in a peer-to-peer network, we could
then share the other server’s feed registry and thus
facilitate subscription to ‘remote’ servers. Another way could
be to manage a centralized feed repository where IoT servers
would publish their feed registry.
Hope this makes sense - looking forward to
discuss more.
Best,
-Regis
