Experience from the field - how customers migrated from Google Cloud IoT Core to Eclipse Hono
summary
Migration replaces Google Cloud IoT Core with Eclipse Hono on GCP and migrates thousands of devices (3,000 in one customer, ~25k growing to 50k in another) with no downtime and no cost increase. Contributions include JWT key auth, Cloud Pub/Sub integration (removing Kafka), a mini digital twin for config/state, a REST device-communication API, an Angular web UI and Terraform GCP deploys. Added dual-connection command routing and device count autoscaling to handle reconnect spikes; outcome is functional but some command-router tuning remains.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:08Why customers chose Hono
- 4:53Open vs closed IoT platforms
- 7:20Why Hono was selected
- 9:48Contributions to Hono
- 14:00Gem One migration
- 20:29Ing Rand migration
- 30:26Benefits of open IoT
- 31:11Q&A
related talks
36mHow we finally migrated an eCommerce-Platform to GCP
01h 02mEclipse IoT: State of the Union
25mImplementing IoT Architectures with Open Source Software
42mRunning your private IoT Cloud Stack
38mHow to Tame My Edge Devices?
45mOpen Source, IoT, and the Big Monster
27mMigrating a Monolith to the Cloud
45mIoT at Google Cloud