<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hybrid on AltSql.com</title>
    <link>https://altsql.com/tags/hybrid/</link>
    <description>Recent content in Hybrid on AltSql.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 02 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://altsql.com/tags/hybrid/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AltSql Is a Native Hybrid of Key-Value and SQL, From the Sensor to the Gateway</title>
      <link>https://altsql.com/altsql-is-a-native-hybrid-of-key-value-and-sql-from-the-sensor-to-the-gateway/</link>
      <pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://altsql.com/altsql-is-a-native-hybrid-of-key-value-and-sql-from-the-sensor-to-the-gateway/</guid>
      <description>&lt;p&gt;AltSql is a native hybrid of key-value and SQL, in the engine and in the database: one small engine and one set of records, from the sensor to the gateway, with nothing to translate in between. Everything else AltSql offers follows from that.&lt;/p&gt;&#xA;&lt;p&gt;The engine is the software. The database is the data the software keeps. The engine is code: it writes records, finds them again, keeps them safe through a power cut and answers questions about them. The database is the records themselves, stored in order, usually in one file. In AltSql the hybrid lives in both. The engine is one piece of code with two ways in, and the database is one set of records that both ways reach.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
