<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Database</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Database feed</description>
    <item>
      <title>Stripe Uses Graph Search and State Machines to Automate Database Remediation</title>
      <link>https://www.infoq.com/news/2026/08/database-remediation-graph/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Database</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/database-remediation-graph/en/headerimage/generatedHeaderImage-1785167911858.jpg"/&gt;&lt;p&gt;The engineering team at Stripe recently described how they automated database incident recovery by modeling their global infrastructure as a graph. Using graph search algorithms together with state machines, the team computes and executes remediation plans automatically.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>GraphDB</category>
      <category>MongoDB</category>
      <category>State-machine</category>
      <category>Database</category>
      <category>Site Reliability Engineering</category>
      <category>Incident Response</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Sun, 09 Aug 2026 06:55:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/database-remediation-graph/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Database</guid>
      <dc:creator>Renato Losio</dc:creator>
      <dc:date>2026-08-09T06:55:00Z</dc:date>
      <dc:identifier>/news/2026/08/database-remediation-graph/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: From ms to µs: OSS Valkey Architecture Patterns for Modern AI</title>
      <link>https://www.infoq.com/presentations/valkey-architecture-patterns/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Database</link>
      <description>&lt;img src="https://res.infoq.com/presentations/valkey-architecture-patterns/en/mediumimage/DumanshuGoyal-medium-1786082640468.jpg"/&gt;&lt;p&gt;Dumanshu Goyal discusses optimizing data layers for low-latency workloads like AI feature stores. Drawing lessons from NASA's Space Shuttle, he explains how proxy architectures introduce hidden CPU costs, elevated tail latencies, and blast-radius risks. He demonstrates how direct-access Valkey architectures achieve microsecond latency, improve resilience, and slash infrastructure costs.&lt;/p&gt; &lt;i&gt;By Dumanshu Goyal&lt;/i&gt;</description>
      <category>Sharding</category>
      <category>QCon San Francisco 2025</category>
      <category>Patterns</category>
      <category>Transcripts</category>
      <category>Performance &amp; Scalability</category>
      <category>Platform Engineering</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>presentation</category>
      <pubDate>Thu, 06 Aug 2026 09:34:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/valkey-architecture-patterns/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Database</guid>
      <dc:creator>Dumanshu Goyal</dc:creator>
      <dc:date>2026-08-06T09:34:00Z</dc:date>
      <dc:identifier>/presentations/valkey-architecture-patterns/en</dc:identifier>
    </item>
    <item>
      <title>Wiz Discloses CosmosEscape, and Practitioners Debate What Customers Could Have Done</title>
      <link>https://www.infoq.com/news/2026/08/cosmosescape-master-key/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Database</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/cosmosescape-master-key/en/headerimage/generatedHeaderImage-1785835623595.jpg"/&gt;&lt;p&gt;Wiz Research disclosed CosmosEscape, a chain that escaped Azure Cosmos DB's Gremlin sandbox and reached a platform-wide key granting read and write access to every database on the service. Microsoft blocked the entry point within two days but took until July 2026 to remove the key. Practitioners debated shared responsibility and what that rearchitecture actually cost.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Access Control</category>
      <category>Azure</category>
      <category>Multi-Tenant Data</category>
      <category>Cloud</category>
      <category>Cloud Architecture</category>
      <category>Database</category>
      <category>Security Vulnerabilities</category>
      <category>Multi-tenancy</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Thu, 06 Aug 2026 09:21:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/cosmosescape-master-key/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Database</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-08-06T09:21:00Z</dc:date>
      <dc:identifier>/news/2026/08/cosmosescape-master-key/en</dc:identifier>
    </item>
  </channel>
</rss>
