+1 for me but let me just sharing with you some considerations ...
If we want to use something like Apache Kafka for storing telemetry data (or maybe events like we already do with ActiveMQ Artemis) then the "telemetry/DEFAULT_TENANT" isn't a valid name for a topic in Kafka (due to the "/" character).
In any case even if we'd like to use Apache Kafka, the Eclipse Hono APIs are designed for being accessible through the AMQP 1.0 protocol : in this case the AMQP - Kafka bridge protocol can be used for bridging the
"telemetry/DEFAULT_TENANT" address (AMQP) to a Kafka topic replacing the "/" with "." (so the real name for the Kafka topic is "telemetry.DEFAULT_TENANT"). It means no problem for senders and receivers which connect to the Hono server and dispatch router (over
AMQP 1.0) for sending/receiving telemetry but through Kafka internally. This configuration was tried in the past and it worked fine.
Just FYI ...
Thanks,
Paolo
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
From: hono-dev-bounces@xxxxxxxxxxx <hono-dev-bounces@xxxxxxxxxxx> on behalf of Dejan Bosanac <dejanb@xxxxxxxxxxxx>
Sent: Wednesday, July 26, 2017 12:07 PM
To: hono developer discussions
Subject: Re: [hono-dev] Custom path separator character
+1 from me as well (as a guilty one for this). We don’t need it anymore