<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Netflix - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Netflix News feed</description>
    <item>
      <title>Netflix Open-Sources Agentic Workflow for Causal Inference</title>
      <link>https://www.infoq.com/news/2026/08/netflix-oci-agent/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Netflix-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/netflix-oci-agent/en/headerimage/generatedHeaderImage-1786886403321.jpg"/&gt;&lt;p&gt;Netflix open-sourced an agentic workflow for Observational Causal Inference (OCI) that reduces toil in causal analysis. Given observational data and the human user's analysis plan, the agent uses an actor-critic loop to estimate causality, write a report, and suggest next steps.&lt;/p&gt; &lt;i&gt;By Anthony Alford&lt;/i&gt;</description>
      <category>Agents</category>
      <category>Agentic AI Architecture</category>
      <category>Netflix</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>news</category>
      <pubDate>Tue, 18 Aug 2026 13:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/netflix-oci-agent/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Netflix-news</guid>
      <dc:creator>Anthony Alford</dc:creator>
      <dc:date>2026-08-18T13:00:00Z</dc:date>
      <dc:identifier>/news/2026/08/netflix-oci-agent/en</dc:identifier>
    </item>
    <item>
      <title>How Netflix Scaled its Real-Time Service Map</title>
      <link>https://www.infoq.com/news/2026/08/netflix-service-topology/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Netflix-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/netflix-service-topology/en/headerimage/Netflix-Service-Topology-Header-1784725848359.jpeg"/&gt;&lt;p&gt;Netflix has described how it redesigned the streaming pipeline behind Service Topology, its real-time service dependencies map, to support production scale. The system uses three stages to separate intermediary resolution from enrichment and persistence, propagates backpressure to Kafka rather than dropping records, and uses server-sent events instead of gRPC for high-volume internal transfers.&lt;/p&gt; &lt;i&gt;By Eran Stiller&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>Microservices</category>
      <category>gRPC</category>
      <category>eBPF</category>
      <category>Netflix</category>
      <category>Apache Kafka</category>
      <category>Distributed Tracing</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Tue, 11 Aug 2026 12:20:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/netflix-service-topology/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Netflix-news</guid>
      <dc:creator>Eran Stiller</dc:creator>
      <dc:date>2026-08-11T12:20:00Z</dc:date>
      <dc:identifier>/news/2026/08/netflix-service-topology/en</dc:identifier>
    </item>
  </channel>
</rss>
