Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [hono-dev] Topology options for client connectivity

Hi Atul,

1) After going through excellent wiki page on topology options, I feel that the option of "connection via Message broker" is more closely aligned with what we are internally discussing at GE.

GE and Red Hat would be at the same page here. Of course I still believe that we should fully support all the other topologies to be sure that we can cover use cases required by all the interested parties.  

Some reasons behind this are as follows:

Our main reason here would be that we already have pretty strong AMQP-based MOM offering and would like to build something on a top of it.

> 2) I understand from recent emails on this topic that 
> "Connection via embedded/dedicated router" seems to be more popular.
> Would this preclude us from using "Connection via Message broker"?

I don't think so. We have to find a way to support all the topologies. :) 

3) We are looking at providing uniform interface to protocol adapters and solutions and provide multiple implementations for it based on underlying MOM/broker. We are looking at hono as that interface.

This is exactly what Red Hat is interested in. To provide protocol adapters and interface definition infrastructure which can be used a facade for IoT clients. 
4) Based on my understanding of initial code contribution it appears that EventDispatcher is responsible for extracting messages from IN exchange and publish it on OUT exchange after applying ACLs. Why do we need an additional component to achieve authorization if underlying MOM can provide the same?

I have the same thoughts about authentication/authorization as you, Atul. I'd like to take a chance to talk with Kai and other folks interested in this topic during the EclipseCon NA. I will send the summary of our brainstorming later here on the list.
5) I also did not see any multi-tenant support (although I did read some posts regarding the same) as part of initial API. Is multi-tenancy support being considered as part of API design for the first milestone?

Hono has to eventually support multi-tenancy. We should design our contributions to do so in order to keep Hono enterprise-grade.
Henryk Konsek

Back to the top