<?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 RollupDB.com</title>
    <link>https://rollupdb.com/tags/iot/</link>
    <description>Recent content in IoT on RollupDB.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rollupdb.com/tags/iot/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Keeping Years of Cold Room Temperatures on an IoT Gateway With RollupDB</title>
      <link>https://rollupdb.com/keeping-years-of-cold-room-temperatures-on-an-iot-gateway-with-rollupdb/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rollupdb.com/keeping-years-of-cold-room-temperatures-on-an-iot-gateway-with-rollupdb/</guid>
      <description>&lt;p&gt;Picture a food distributor with six cold rooms, each with a sensor that reports the temperature every second. The readings go to a small gateway in the building. Somebody will want two things from that data. Today: is any room warming up? Two years from now, during an audit or an insurance claim: what were the temperatures in room 4 last March, and how bad did it get?&lt;/p&gt;&#xA;&lt;p&gt;Raw readings don&amp;rsquo;t fit that brief. Six sensors at one reading a second come to about 190 million readings a year, and nobody wants to keep that on a gateway or ship it all to the cloud just to answer a question once a year. What the audit needs is the coldest, the warmest, the average and the spread for each room, hour by hour. That&amp;rsquo;s what RollupDB keeps.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
