<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Amazon Web Services - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Amazon Web Services Articles feed</description>
    <item>
      <title>Article: Building Streaming Infrastructure That Scales: Because Viewers Won't Wait until Tomorrow</title>
      <link>https://www.infoq.com/articles/evolution-backend-streaming-application/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Amazon+Web+Services-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/evolution-backend-streaming-application/en/headerimage/header-evolution-backend-streaming-application-1766049421558.jpg"/&gt;&lt;p&gt;In streaming, the challenge is immediate: customers are watching TV right now, not planning to watch it tomorrow. When systems fail during prime time, there is no recovery window; viewers leave and may not return. One and a half years ago, at ProSiebenSat.1 Media SE, we faced the challenge of scaling streaming applications for international users.&lt;/p&gt; &lt;i&gt;By Daniele Frasca&lt;/i&gt;</description>
      <category>Architecture</category>
      <category>QCon Software Development Conference</category>
      <category>Amazon Web Services</category>
      <category>Event Stream Processing</category>
      <category>InfoQ Dev Summit Munich 2025</category>
      <category>Cloud</category>
      <category>Microservices</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Tue, 23 Dec 2025 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/evolution-backend-streaming-application/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Amazon+Web+Services-articles</guid>
      <dc:creator>Daniele Frasca</dc:creator>
      <dc:date>2025-12-23T09:00:00Z</dc:date>
      <dc:identifier>/articles/evolution-backend-streaming-application/en</dc:identifier>
    </item>
  </channel>
</rss>
