Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [hono-dev] Hono specifications and standards

Thanks for the quick reply Kai, and I really appreciate the welcome

I have been reviewing the documentation that’s available and I have a few areas where I’m not clear – most likely because I was absent from the opening discussions.  My apologies

At a high-level some initial questions about the vision I have are

1.  Is Hono focused on 
  • building an IoT server that securely flows messages and execute workload 
  • or codifying client payload patterns that can be understood as generically actionable on north and southbound clients.  IE – heres a payload that means we want to update our firmware with the attached binary
2.  Will Hono allow multiple applications to run at once in isolation(Co-tenanted, or like Tomcat hosting many Web Applications at once) - I think the answer is yes, and it looks like they are called “Solutions”?

3.  What does the schema / meta-model of a “Solution” look like?

4.  I see interesting thoughts about topic level ACL define applied to users and devices.   Is the user/device registry intended to be extensible or injectable to third party solutions and auth strategies?    

5.  Is there persistent or at-rest data storage in this design?  Maybe something like a session or state

These questions felt more like belonged on the developer discussion, but I’m happy to do issues in github and remove the noise.

Full disclosure – ClearBlade is a company that offers a commercial IoT Platform.  Any opportunity to contribute ideas and code to the Hono project that helps us all standardize and interoperate would be great for the IoT developer community.

Aaron Allsbrook | CTO | ClearBlade
103 E. 5th Street | Austin, TX 78701

From: <hono-dev-bounces@xxxxxxxxxxx> on behalf of Kai <>
Reply-To: hono developer discussions <hono-dev@xxxxxxxxxxx>
Date: Sunday, February 28, 2016 at 9:55 AM
To: hono developer discussions <hono-dev@xxxxxxxxxxx>
Subject: Re: [hono-dev] Hono specifications and standards

Hi Aaron,

thanks a lot for your interest! There definitely is opportunity to contribute ideas (and code :-)). All of the ideas we have for the project so far are described on the project home page at Eclipse [1], the GitHub repo issues [2] and the mailing list (which you already seem to have found :-)). Feel free to share your thoughts and/or create issues on GitHub and the mailing list.

We are at a very early stage regarding architecture discussions but it seems settled that we will provide an AMQP 1.0 based API for clients to connect and interact with Hono. It also seems to be agreed upon that we will support multiple "messaging engines" under the hood, in particular I see RabbitMQ and Kafka in that area. Since we also have people from RedHat involved we will probably also support Active MQ (but you should ask for confirmation on the mailing list). We also strive for supporting deployment to runtime environments based on Docker as well as Cloud Foundry.


On Sun, Feb 28, 2016 at 3:58 PM Aaron Allsbrook <aallsbrook@xxxxxxxxxxxxxx> wrote:
I am very interested in the Hono project and the potential capabilities it offers.  I believe there is opportunity for Hono to provide open functionality, and also lead the IoT community in some core application standards.  

Specifically things like API specification, securing of messages and application schema export between server instances.  Is there any documentation on whats being planned in this space?  Is there an opportunity to contribute ideas?

Aaron Allsbrook | CTO | ClearBlade
103 E. 5th Street | Austin, TX 78701

hono-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top