<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Iot on App Coding</title>
    <link>https://appcoding.com/tags/iot/</link>
    <description>Recent content in Iot on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 02 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/iot/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AltSql: Gives IoT Devices a 15 KB Database That Keeps Working When the Link Drops</title>
      <link>https://appcoding.com/altsql-gives-iot-devices-a-15-kb-database-that-keeps-working-when-the-link-drops/</link>
      <pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/altsql-gives-iot-devices-a-15-kb-database-that-keeps-working-when-the-link-drops/</guid>
      <description>&lt;p&gt;Anyone who has built the software side of a connected product knows the integration job. The device keeps its readings and settings in one format and the gateway or cloud service wants those same values as rows in a SQL database. Somebody writes a converter. Then somebody has to keep that converter alive for as long as the device stays in the field, which for industrial equipment or embedded systems can easily be ten years. The converter has to handle offline periods, retries, out-of-order updates, and the device&amp;rsquo;s own data format changing over time.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
