Eclipse Hono 0.5
- Devices can publish Telemetry data and Events
- Support for MQTT, HTTP and Kura
- Support for HTTP Basic Auth and MQTT username/password authentication
- Horizontal scalability
- Central management of device identities and credentials
- Multi tenancy
- Applications can consume data per tenant
- End-to-end message flow control
Since this is the initial release there are no incompatibilities with previous versions.
Hono does not (yet) contain interactive user interfaces which would require localization to specific languages.
Hono is implemented as a set of micro services. The primary artifacts are Docker images which can be deployed to arbitrary container orchestration frameworks. In particular, Hono supports deployment to Kubernetes, OpenShift and Docker Swarm.
|0.5-M10||2017/10/24||Created Eclipse sandbox, Arbitrary bug fixes and improvements|
|0.5-M9||2017/10/10||Protocol Adapters now require devices to authenticate on connection establishment. Device Registry exposes RESTful resources for managing credentials via HTTP. Protocol Adapters expose additional metrics indicating number of processed/discarded messages.|
|0.5-M8||2017/08/11||The Device Registry now exposes RESTful resources accessible via HTTP which represent the operations of the Device Registration API. This is in addition to the standard AMQP 1.0 based Device Registration endpoint. In exchange, the HTTP Adapter no longer exposes these resources, i.e. device can no longer be registered using the HTTP Adapter. In subsequent milestones the Device Registry will be extended to also expose the Credentials API by means of RESTful resources accessible via HTTP. Please note that the RESTful resources do not constitute an official Hono API, i.e. the Device Registration API and the Credentials API are still defined by means of AMQP 1.0 message exchanges only. The REST API is simply provided for convenience, so that it is easier to e.g. register a device from the command line using tools like curl and/or HTTPie.|