In my last post, I introduced CultivatorsLedger — a local-first cultivation telemetry platform built...
In my last post, I introduced CultivatorsLedger — a local-first cultivation telemetry platform built on Next.js, PostgreSQL, and Docker.
One of the first architectural decisions I made was how to handle sensor data ingestion. In a grow environment, WiFi is not reliable. Network drops happen. And when they do, standard HTTP posts lose data.
I needed a queue.
The Contenders
I looked at three options:
Why this combination keeps winning for IoT telemetry backends — not in a benchmark, but against flaky...
MQTT in the Wild: What Industrial Monitoring Taught Me About Resilient Messaging For web...
Why I wrote this After I got one app working on MinIO, I thought I understood the...
In 2017 I was maintaining a Node.js ecommerce server when a new project landed on my desk — an IoT...
A practical comparison of MQTT and HTTP for IoT, based on production work with robot platforms, warehouse sensors, dashboards,…
Stop sending raw sensor data to the cloud. A deep dive into edge processing, local LLM routing, and the privacy hard-wall for…
