<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>databases on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/databases/</link>
    <description>Recent content in databases on Agile Software Development</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 02 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agilesoftdev.com/tags/databases/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AltSql: Lets IoT Teams Ship Products That Work Offline and Sync Automatically</title>
      <link>https://agilesoftdev.com/altsql-lets-iot-teams-ship-products-that-work-offline-and-sync-automatically/</link>
      <pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/altsql-lets-iot-teams-ship-products-that-work-offline-and-sync-automatically/</guid>
      <description>Teams building connected products face a design choice that kills agility: either the device depends on the server for everything, or you build a converter that keeps two data formats in sync. The device has readings and settings in its own format. The server wants those same values as SQL rows. Somebody writes a converter. Then somebody has to keep that converter alive and correct for ten years.
The converter approach is why IoT teams move slowly.</description>
    </item>
    
    <item>
      <title>Precomputing: Keeps Dashboards Fast Without Slowing Development Cycles</title>
      <link>https://agilesoftdev.com/precomputing-keeps-dashboards-fast-without-slowing-development-cycles/</link>
      <pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/precomputing-keeps-dashboards-fast-without-slowing-development-cycles/</guid>
      <description>Teams that ship features fast need dashboards that answer questions instantly. The usual pattern is to recalculate answers on every refresh, or to ship all your data to a hosted analytics service and wait for it to ingest. Both approaches have the same problem: the dashboard either waits for the query, or you pay for scale you don&amp;rsquo;t need most of the time. In either case, answering a question about your product becomes a friction point.</description>
    </item>
    
  </channel>
</rss>
