[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [hono-dev] Command and Control / Cloud to Device
|
On 12/03/18 12:38, Marc Pellmann wrote:
The biggest question in the moment seems to be if one AMQP link per
connected device is a realistic architecture option for us?
This means for each device, that connects to an adapter the adapter will
create a receiver link with a Hono messaging instance and Hono messaging
with the Router network. Also a consumer application instance creates a
sender link with the Router network for each device, to which it wants
to send a command as soon as this is connected.
Just for completeness, if using message routing, the application would
need to have a separate link for each device it wishes to send to. It
could use a so-called 'anonymous sender', with the address of the device
specified in the 'to' field on the message.
Then for example there is a tenant with an application to handle 1
million devices (number of registered devices). We assume there are a
number of adapter and messaging instances to handle this - so maybe
50.000 devices connect to each (MQTT) adapter. Behind is the Dispatch
Router network with also a number of instances. I assume also the
application is scaled.
When all devices are connected we have 1 million links, which will be
routed through the Dispatch Router network (from e.g. 10 Hono messaging
instances and 5 application instances). Also the creation of such links
should be in time (azure for example says 100/sec device connections per
S1 instance).
@Gordon, @Dejan, @Paolo - do you think this a realistic option?
Having a million receivers and senders attached to a router network and
communicating using message routing is certainly realistic (tests of
that scale have been carried out, though on bare metal only at present).
I'm not aware of tests of link routing at that scale, which is not to
say it is not realistic, just that it should be investigated further.
