<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Edge Computing on Rusty Eddy</title><link>https://rustyeddy.com/tags/edge-computing/</link><description>Recent content in Edge Computing on Rusty Eddy</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 31 May 2026 09:35:53 -0700</lastBuildDate><atom:link href="https://rustyeddy.com/tags/edge-computing/index.xml" rel="self" type="application/rss+xml"/><item><title>The Five Layers of a Practical IoT System</title><link>https://rustyeddy.com/iot/iot-system-architecture-explained/</link><pubDate>Sat, 15 Nov 2025 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/iot/iot-system-architecture-explained/</guid><description>A practical five-layer model for IoT architecture, grounded in the OttO edge runtime and the Gardener reference application.</description></item><item><title>IoT System Architecture (Device to Cloud)</title><link>https://rustyeddy.com/iot/iot-system-architecture-device-to-cloud/</link><pubDate>Fri, 13 Jan 2023 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/iot/iot-system-architecture-device-to-cloud/</guid><description>&lt;p&gt;This page is a diagram-first overview of the IoT architecture used throughout
the projects on this site. It is for engineers who need to decide where device
logic ends, where edge coordination begins, and how telemetry, control, APIs,
storage, and user interfaces fit together.&lt;/p&gt;
&lt;p&gt;The goal is not to present a single correct design. The goal is to show a
reasonable baseline that can grow beyond demos without locking the system to
one board, one sensor, one database, or one user interface.&lt;/p&gt;</description></item><item><title>Adding MQTT to the IoT Gateway</title><link>https://rustyeddy.com/iot/iot-gateway-mqtt/</link><pubDate>Tue, 29 Mar 2022 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/iot/iot-gateway-mqtt/</guid><description>A practical MQTT implementation note for the OttO IoT gateway, covering topic design, subscriptions, callbacks, testing, and memory boundaries.</description></item></channel></rss>