<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Next Verticals on AltSql.com</title>
    <link>https://altsql.com/tags/next-verticals/</link>
    <description>Recent content in Next Verticals on AltSql.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 25 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://altsql.com/tags/next-verticals/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Next Verticals: Eight Industries Where a Database on the Sensor Could Fit</title>
      <link>https://altsql.com/next-verticals-eight-industries-where-a-database-on-the-sensor-could-fit/</link>
      <pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://altsql.com/next-verticals-eight-industries-where-a-database-on-the-sensor-could-fit/</guid>
      <description>&lt;p&gt;The three case studies share one pattern. A device keeps its own data, decides for itself and talks over a link that is slow, costly or often down. Its gateway receives the same records the device wrote, so nobody has to maintain code that translates between the two. Machine monitoring, cold chain and agriculture came first because the Alpha demo covers them.&lt;/p&gt;&#xA;&lt;p&gt;The pattern turns up in many more industries. None of the eight below has been tested, and none has a device in the Beta. This post sets out what each would ask of the engine, what already carries over from the demo, and what would be new work. It is a map for choosing what to try after the Beta, ideally together with people who build these devices.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
