Eclipse Hono provides a lot of value to organizations that want to build scalable IoT cloud platforms. It defines both communication and device identity APIs necessary to build truly scalable, multi-tenant IoT connectivity service. But, by design, Hono doesn't provide a single implementation and allows APIs and the building blocks to be used to build different products in various environments.
One such product is Red Hat AMQ Online, a messaging-as-service cloud platform for OpenShift, which recently introduced an IoT connectivity as a feature. In this session we'll describe the process we went through to build this feature using Eclipse Hono as a foundation layer. We'll discuss how we adjusted various concepts of Hono to the existing product and implemented missing parts. We'll talk about tenancy model, addressing model, device registry, operator deployment and so on. These valuable lessons can help organizations that are planning (or just considering) to go through the same process.
