<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ News 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=news</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>Site Reliability Engineering</category>
      <category>State-machine</category>
      <category>GraphDB</category>
      <category>Database</category>
      <category>MongoDB</category>
      <category>Incident Response</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</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=news</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>Cloudflare's Precursor Detects Bots and AI Agents Through Continuous Behavioral Analysis</title>
      <link>https://www.infoq.com/news/2026/08/cloudflare-precursor-detection/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/cloudflare-precursor-detection/en/headerimage/generatedHeaderImage-1784634999305.jpg"/&gt;&lt;p&gt;Cloudflare recently introduced Precursor, a client-side behavioral analysis engine that continuously evaluates session interactions, such as mouse movements and keyboard timing, to improve detection of sophisticated bots and AI agents without relying solely on one-time challenges like CAPTCHAs.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>AI Security</category>
      <category>Cloudflare</category>
      <category>Cloud</category>
      <category>Cloud Security</category>
      <category>BOTS</category>
      <category>Authentication</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Sat, 08 Aug 2026 07:54:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/cloudflare-precursor-detection/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=news</guid>
      <dc:creator>Renato Losio</dc:creator>
      <dc:date>2026-08-08T07:54:00Z</dc:date>
      <dc:identifier>/news/2026/08/cloudflare-precursor-detection/en</dc:identifier>
    </item>
    <item>
      <title>GitHub Hardens npm and Actions Defaults, Drawing Debate over Delays versus Signing</title>
      <link>https://www.infoq.com/news/2026/08/github-npm-actions-defaults/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/github-npm-actions-defaults/en/headerimage/generatedHeaderImage-1785830307506.jpg"/&gt;&lt;p&gt;GitHub consolidated the npm and Actions changes it shipped from March to July 2026 against supply chain attacks, several of which alter defaults rather than add options. Hacker News discussion focused less on the individual controls than on whether waiting periods are the right instrument, or a substitute for author-side package signing.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>github</category>
      <category>Continuous Delivery</category>
      <category>Open Source</category>
      <category>GitHub Actions</category>
      <category>Automation</category>
      <category>Software Supply Chain</category>
      <category>Security</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Sat, 08 Aug 2026 07:45:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/github-npm-actions-defaults/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=news</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-08-08T07:45:00Z</dc:date>
      <dc:identifier>/news/2026/08/github-npm-actions-defaults/en</dc:identifier>
    </item>
    <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=news</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>Agents</category>
      <category>Containers</category>
      <category>Large language models</category>
      <category>Isolates</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</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=news</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=news</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>Artificial Intelligence</category>
      <category>Site Reliability Engineering</category>
      <category>Model Context Protocol (MCP)</category>
      <category>Operational Intelligence</category>
      <category>Developer Experience</category>
      <category>Large language models</category>
      <category>Distributed Systems</category>
      <category>Reliability</category>
      <category>Incident Response</category>
      <category>Slack</category>
      <category>Platform Engineering</category>
      <category>Observability</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</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=news</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=news</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>Incident Response</category>
      <category>Observability</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</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=news</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>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=news</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=news</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=news</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=news</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=news</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>Model Context Protocol (MCP)</category>
      <category>Generative AI</category>
      <category>Cloud</category>
      <category>Azure</category>
      <category>API Gateway</category>
      <category>Microsoft Azure</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>Development</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=news</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=news</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>NPM</category>
      <category>Security Vulnerabilities</category>
      <category>Open Source</category>
      <category>Application Security</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=news</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=news</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>Leadership</category>
      <category>Kubernetes</category>
      <category>User Experience</category>
      <category>Developer Experience</category>
      <category>Collaboration</category>
      <category>Teamwork</category>
      <category>Product Development</category>
      <category>Architecture</category>
      <category>Topology</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=news</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>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=news</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>Security Vulnerabilities</category>
      <category>Cloud Architecture</category>
      <category>Cloud</category>
      <category>Database</category>
      <category>Access Control</category>
      <category>Azure</category>
      <category>Multi-Tenant Data</category>
      <category>Multi-tenancy</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>Development</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=news</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>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=news</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>Agents</category>
      <category>AI Architecture</category>
      <category>Kubernetes</category>
      <category>Cloud Native Architecture</category>
      <category>Cloud Native Computing Foundation</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>Development</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=news</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>
    <item>
      <title>Vercel Labs Ships Zero: a Graph-First Language Built So Agents Write the Code</title>
      <link>https://www.infoq.com/news/2026/08/vercel-ships-zero-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=news</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;Vercel Labs has introduced Zero, an experimental systems programming language aimed at AI rather than human users. It employs unique features like a specific toolchain contract and structured error messages. Reaching version 0.3.4, it compiles to native binaries for major operating systems. The language prioritizes size, speed, and agent usability, though it is still in development.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Agents</category>
      <category>Go Language</category>
      <category>Web Development</category>
      <category>Rust</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 06 Aug 2026 05:51:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/vercel-ships-zero-ai/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=news</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-08-06T05:51:00Z</dc:date>
      <dc:identifier>/news/2026/08/vercel-ships-zero-ai/en</dc:identifier>
    </item>
    <item>
      <title>JioHotstar Explains the Distributed Engineering behind Personalized Ad Requests at Streaming Scale</title>
      <link>https://www.infoq.com/news/2026/08/jiohotstar-ad-decisioning-flow/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/jiohotstar-ad-decisioning-flow/en/headerimage/generatedHeaderImage-1785711356085.jpg"/&gt;&lt;p&gt;JioHotstar explains the distributed architecture behind its real-time ad request workflow, covering ad decisioning, waterfall tiering, pacing algorithms, latency optimization, and service coordination required to select and deliver personalized advertisements during streaming playback at scale.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Data-Driven Decision Making Series</category>
      <category>Video Codec</category>
      <category>Architecture</category>
      <category>Streaming</category>
      <category>Scalability</category>
      <category>Microservices</category>
      <category>Algorithms</category>
      <category>Decision Trees</category>
      <category>Streaming Video</category>
      <category>Distributed Systems</category>
      <category>Technology</category>
      <category>Low Latency</category>
      <category>Advertising</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Wed, 05 Aug 2026 14:09:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/jiohotstar-ad-decisioning-flow/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=news</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-08-05T14:09:00Z</dc:date>
      <dc:identifier>/news/2026/08/jiohotstar-ad-decisioning-flow/en</dc:identifier>
    </item>
  </channel>
</rss>
