<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ feed</description>
    <item>
      <title>Cloudflare Launches Persistent, Stateful, Computer-like Environments for Agents</title>
      <link>https://www.infoq.com/news/2026/08/cloudflare-computer-agents/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/cloudflare-computer-agents/en/headerimage/cloudflare-computer-agents-1786134762378.jpeg"/&gt;&lt;p&gt;Cloudflare has introduced Cloudflare Computer, a new open-source runtime designed to give AI agents something closer to a real "computer" instead of just ephemeral containers. It leverages Cloudflare isolates for fast serverless execution, making agents cheaper, faster, and more scalable, according to the company.&lt;/p&gt; &lt;i&gt;By Sergio De Simone&lt;/i&gt;</description>
      <category>Isolates</category>
      <category>Containers</category>
      <category>Large language models</category>
      <category>Agents</category>
      <category>Development</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 21:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/cloudflare-computer-agents/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Sergio De Simone</dc:creator>
      <dc:date>2026-08-07T21:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/cloudflare-computer-agents/en</dc:identifier>
    </item>
    <item>
      <title>Instacart Builds Blueberry, an AI-Powered Assistant to Help On-Call Engineers Investigate Incidents</title>
      <link>https://www.infoq.com/news/2026/08/instacart-blueberry-sre-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/instacart-blueberry-sre-ai/en/headerimage/generatedHeaderImage-1785721280661.jpg"/&gt;&lt;p&gt;Instacart introduced Blueberry, an AI-assisted incident response system that helps on-call engineers investigate production issues faster. It combines AI agents, operational data, and historical incident knowledge to generate grounded root cause hypotheses in Slack. It uses parallel subagents, MCP integrations, and incident history to reduce investigation time while keeping engineers in control.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>Reliability</category>
      <category>Large language models</category>
      <category>Artificial Intelligence</category>
      <category>Site Reliability Engineering</category>
      <category>Model Context Protocol (MCP)</category>
      <category>Operational Intelligence</category>
      <category>Developer Experience</category>
      <category>Slack</category>
      <category>Incident Response</category>
      <category>Platform Engineering</category>
      <category>Observability</category>
      <category>Development</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 14:34:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/instacart-blueberry-sre-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-08-07T14:34:00Z</dc:date>
      <dc:identifier>/news/2026/08/instacart-blueberry-sre-ai/en</dc:identifier>
    </item>
    <item>
      <title>AI Is Transforming Incident Response - but the Hardest Problems May Still Belong to Humans</title>
      <link>https://www.infoq.com/news/2026/08/ai-incident-response/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/ai-incident-response/en/headerimage/generatedHeaderImage-1785503516175.jpg"/&gt;&lt;p&gt;Artificial intelligence is rapidly changing how engineering teams respond to production incidents, offering the ability to summarize incident channels, analyze unfamiliar code, suggest remediation steps, generate pull requests, and increasingly assist with diagnosis.&lt;/p&gt; &lt;i&gt;By Craig Risi&lt;/i&gt;</description>
      <category>Artificial Intelligence</category>
      <category>Observability</category>
      <category>Incident Response</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 12:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/ai-incident-response/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Craig Risi</dc:creator>
      <dc:date>2026-08-07T12:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/ai-incident-response/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: Rewriting All of Spotify's Code Base, All the Time</title>
      <link>https://www.infoq.com/presentations/spotify-ai-codebase-migration-agent/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/presentations/spotify-ai-codebase-migration-agent/en/mediumimage/medium-1784809804876.jpg"/&gt;&lt;p&gt;Jo Kelly-Fenton and Aleksandar Mitic explain how Spotify created "Honk," an AI coding agent, to handle complex fleet-wide codebase migrations. They share key architectural insights on decoupling CI verification runtimes from AI agents, dealing with automated pull request bottlenecks, and driving aggressive standardization across thousands of engineering repositories.&lt;/p&gt; &lt;i&gt;By Jo Kelly-Fenton, Aleksandar Mitic&lt;/i&gt;</description>
      <category>QCon London 2026</category>
      <category>AI Coding</category>
      <category>Continuous Improvement</category>
      <category>migration</category>
      <category>Large language models</category>
      <category>Standardization</category>
      <category>Agents</category>
      <category>Continuous Delivery</category>
      <category>Transcripts</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>presentation</category>
      <pubDate>Fri, 07 Aug 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/spotify-ai-codebase-migration-agent/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Jo Kelly-Fenton, Aleksandar Mitic</dc:creator>
      <dc:date>2026-08-07T11:00:00Z</dc:date>
      <dc:identifier>/presentations/spotify-ai-codebase-migration-agent/en</dc:identifier>
    </item>
    <item>
      <title>Article: InfoQ Culture and Methods Trends Report - 2026</title>
      <link>https://www.infoq.com/articles/culture-trends-2026/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/articles/culture-trends-2026/en/headerimage/graph-trends-report-2026-cm-1785761407624.jpg"/&gt;&lt;p&gt;This report summarizes how the InfoQ Culture and Methods editorial team sees the ongoing and emergent trends in the culture and methods space in 2026.&lt;/p&gt; &lt;i&gt;By Shane Hastie, Ben Linders, Vanessa Formicola, Shawna Martell, Rafiq Gemmail, Craig Smith, Phillip Mortimer, Yinka Omole&lt;/i&gt;</description>
      <category>Ethics</category>
      <category>Psychological Safety</category>
      <category>Teamwork</category>
      <category>Collaboration</category>
      <category>Artificial Intelligence</category>
      <category>InfoQ Trends Report 2026</category>
      <category>Platform Engineering</category>
      <category>Culture &amp; Methods</category>
      <category>article</category>
      <pubDate>Fri, 07 Aug 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/culture-trends-2026/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Shane Hastie, Ben Linders, Vanessa Formicola, Shawna Martell, Rafiq Gemmail, Craig Smith, Phillip Mortimer, Yinka Omole</dc:creator>
      <dc:date>2026-08-07T09:00:00Z</dc:date>
      <dc:identifier>/articles/culture-trends-2026/en</dc:identifier>
    </item>
    <item>
      <title>Podcast: Culture &amp; Methods Trends 2026: The Human Side of AI Engineering</title>
      <link>https://www.infoq.com/podcasts/infoq-culture-trends-2026/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/podcasts/infoq-culture-trends-2026/en/smallimage/infoQ-trends-report-podcast-logo-big-1785405371110.jpg"/&gt;&lt;p&gt;This is the Engineering Culture Trends Report for 2026.  Featuring a panel of QCon speakers and InfoQ contributors, they discussed AI adoption maturity and risk, the transformation of engineering team structures and roles, and the human dimensions of software development that must not be lost in 2026.&lt;/p&gt; &lt;i&gt;By Ben Linders, Rafiq Gemmail, Craig Smith, Vanessa Formicola, Shawna Martell, Phillip Mortimer, Yinka Omole&lt;/i&gt;</description>
      <category>Accessibility</category>
      <category>Quality</category>
      <category>Technology</category>
      <category>InfoQ Trends Report</category>
      <category>Agile Education</category>
      <category>Software Development</category>
      <category>Careers</category>
      <category>Teamwork</category>
      <category>Psychological Safety</category>
      <category>Training / Certification</category>
      <category>Collaboration</category>
      <category>Testing</category>
      <category>Productivity</category>
      <category>Developer Experience</category>
      <category>Engineering Culture Podcast</category>
      <category>InfoQ Trends Report 2026</category>
      <category>Leadership</category>
      <category>Green Software</category>
      <category>Platform Engineering</category>
      <category>Observability</category>
      <category>Culture &amp; Methods</category>
      <category>podcast</category>
      <pubDate>Fri, 07 Aug 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/podcasts/infoq-culture-trends-2026/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Ben Linders, Rafiq Gemmail, Craig Smith, Vanessa Formicola, Shawna Martell, Phillip Mortimer, Yinka Omole</dc:creator>
      <dc:date>2026-08-07T09:00:00Z</dc:date>
      <dc:identifier>/podcasts/infoq-culture-trends-2026/en</dc:identifier>
    </item>
    <item>
      <title>Uno Platform 6.6 Adds Native AOT, Vulkan Rendering, and Broader Accessibility Support</title>
      <link>https://www.infoq.com/news/2026/08/uno-platform-6-6/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/uno-platform-6-6/en/headerimage/header-1670341892423-1785867079887.jpg"/&gt;&lt;p&gt;Uno Platform 6.6 introduces Native AOT publishing across five target platforms, an optional Vulkan rendering backend, and automatic registration for the framework’s Model Context Protocol servers. The release also reduces XAML boilerplate, expands cross-platform WinUI API coverage, and improves accessibility and multilingual text handling.&lt;/p&gt; &lt;i&gt;By Edin Kapić&lt;/i&gt;</description>
      <category>Uno Platform</category>
      <category>.NET</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 08:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/uno-platform-6-6/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Edin Kapić</dc:creator>
      <dc:date>2026-08-07T08:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/uno-platform-6-6/en</dc:identifier>
    </item>
    <item>
      <title>Rootly Drops Small PR Rule as Agentic AI Changes Code Review Economics</title>
      <link>https://www.infoq.com/news/2026/08/rootly-small-pr-agentic-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/rootly-small-pr-agentic-ai/en/headerimage/generatedHeaderImage-1786029342014.jpg"/&gt;&lt;p&gt;Incident management platform provider Rootly has published an account of its decision to drop its long-standing small pull request rule, arguing that the practice no longer serves its purpose now that AI agents generate most of its code. The company describes a shift from measuring PR size to assessing blast radius, with feature flags and rollback capability taking precedence over line counts.&lt;/p&gt; &lt;i&gt;By Matt Saunders&lt;/i&gt;</description>
      <category>Agents</category>
      <category>Code Reviews</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 08:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/rootly-small-pr-agentic-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Matt Saunders</dc:creator>
      <dc:date>2026-08-07T08:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/rootly-small-pr-agentic-ai/en</dc:identifier>
    </item>
    <item>
      <title>Azure API Management Adds Dedicated AI Gateway Tier, Governing Models and MCP Tools</title>
      <link>https://www.infoq.com/news/2026/08/azure-apim-ai-gateway-tier/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/azure-apim-ai-gateway-tier/en/headerimage/generatedHeaderImage-1785739180016.jpg"/&gt;&lt;p&gt;Microsoft released a dedicated AI Gateway tier of Azure API Management in public preview, with a control plane built around models, MCP servers and tools rather than APIs. It fronts Foundry, Bedrock, Vertex AI and OpenAI behind one endpoint, with policy cards instead of XML. Architects welcomed the consolidation while questioning where the governance boundary sits.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Generative AI</category>
      <category>Azure</category>
      <category>API Gateway</category>
      <category>Cloud</category>
      <category>Model Context Protocol (MCP)</category>
      <category>Microsoft Azure</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 06:35:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/azure-apim-ai-gateway-tier/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-08-07T06:35:00Z</dc:date>
      <dc:identifier>/news/2026/08/azure-apim-ai-gateway-tier/en</dc:identifier>
    </item>
    <item>
      <title>npm Staged Publishing Available, Adding a Human Approval Step Before Packages Go Live</title>
      <link>https://www.infoq.com/news/2026/08/npm-stage-available/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;npm has introduced staged publishing for Node.js, requiring maintainer approval before a version is installable. Versions are queued and must pass a two-factor authentication challenge for release. This feature aims to enhance security amid rising supply chain threats. It is available in npm CLI 11.15.0+ and Node 22.14.0+, alongside new configurable permission flags.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Open Source</category>
      <category>Application Security</category>
      <category>NPM</category>
      <category>Security Vulnerabilities</category>
      <category>Web Development</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 07 Aug 2026 06:12:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/npm-stage-available/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-08-07T06:12:00Z</dc:date>
      <dc:identifier>/news/2026/08/npm-stage-available/en</dc:identifier>
    </item>
    <item>
      <title>From Projects to Products: Turning Platforms into Products People Use</title>
      <link>https://www.infoq.com/news/2026/08/platform-products-people-use/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/platform-products-people-use/en/headerimage/generatedHeaderImage-1785611764573.jpg"/&gt;&lt;p&gt;Having a platform is not enough; the real challenge is ensuring that it is understandable, usable, and actually adopted by its users.  A capability is done when it can be reliably used by others. To evaluate progress, you can ask yourself “Is this being used?” and “Does it reduce friction for users?” This can help align development work with actual user value rather than delivery,&lt;/p&gt; &lt;i&gt;By Ben Linders&lt;/i&gt;</description>
      <category>Architecture</category>
      <category>Topology</category>
      <category>Teamwork</category>
      <category>Collaboration</category>
      <category>Product Development</category>
      <category>Kubernetes</category>
      <category>Developer Experience</category>
      <category>Leadership</category>
      <category>User Experience</category>
      <category>Platforms</category>
      <category>Platform Engineering</category>
      <category>Development</category>
      <category>Culture &amp; Methods</category>
      <category>news</category>
      <pubDate>Thu, 06 Aug 2026 11:59:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/platform-products-people-use/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Ben Linders</dc:creator>
      <dc:date>2026-08-06T11:59:00Z</dc:date>
      <dc:identifier>/news/2026/08/platform-products-people-use/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=global</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=global</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=global</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=global</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>
    <item>
      <title>Article: Runtime-Agnostic AI Workflows: A Pattern for Production Durability and Fast Eval Iteration</title>
      <link>https://www.infoq.com/articles/ai-workflow-pattern/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/articles/ai-workflow-pattern/en/headerimage/header-1785766770921.jpg"/&gt;&lt;p&gt;AI workflows have two needs that trade off directly. Running reliably in production requires persisting and distributing every step so it survives crashes, deploys, and restarts. But that same machinery is what makes runs too heavy for the fast, throwaway loop you need to check an LLM's output quality. The properties that buy durability are the ones that kill iteration speed.&lt;/p&gt; &lt;i&gt;By Mateus Moury&lt;/i&gt;</description>
      <category>Large language models</category>
      <category>Agents</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>article</category>
      <pubDate>Thu, 06 Aug 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/ai-workflow-pattern/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Mateus Moury</dc:creator>
      <dc:date>2026-08-06T09:00:00Z</dc:date>
      <dc:identifier>/articles/ai-workflow-pattern/en</dc:identifier>
    </item>
    <item>
      <title>Pods as Workers, Not Agents: Rethinking the Deployment Unit for AI Agents on Kubernetes</title>
      <link>https://www.infoq.com/news/2026/08/pod-deployment-unit-ai-agents/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/pod-deployment-unit-ai-agents/en/headerimage/header-1785763169197.jpeg"/&gt;&lt;p&gt;Running AI agents on Kubernetes raises a key question: should each agent get its own Pod? The kagent project argues no—agents are bursty, short-lived, can spawn subagents, and may wait for human approval, making one Pod per agent wasteful. Agent-substrate adds a control plane to schedule logical “Actors” onto long-lived worker Pods.&lt;/p&gt; &lt;i&gt;By Mark Silvester&lt;/i&gt;</description>
      <category>Cloud Native Computing Foundation</category>
      <category>Cloud Native Architecture</category>
      <category>Agents</category>
      <category>AI Architecture</category>
      <category>Kubernetes</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Thu, 06 Aug 2026 06:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/pod-deployment-unit-ai-agents/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Mark Silvester</dc:creator>
      <dc:date>2026-08-06T06:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/pod-deployment-unit-ai-agents/en</dc:identifier>
    </item>
  </channel>
</rss>
