<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Serverless</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Serverless feed</description>
    <item>
      <title>AWS Lambda Pushes Serverless toward Long-Running Workloads</title>
      <link>https://www.infoq.com/news/2026/09/lambda-90-minute-timeout/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Serverless</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/09/lambda-90-minute-timeout/en/headerimage/generatedHeaderImage-1789110995851.jpg"/&gt;&lt;p&gt;AWS Lambda now allows functions running on Lambda Managed Instances to run for up to 90 minutes, six times longer than the previous 15-minute limit, further blurring the line between a Lambda invocation and a traditional server. The limit remains unchanged for traditional synchronous requests.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>Serverless</category>
      <category>AWS Lambda</category>
      <category>Cloud</category>
      <category>AWS</category>
      <category>Event Driven Architecture</category>
      <category>Cloud Computing</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Sat, 19 Sep 2026 09:11:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/lambda-90-minute-timeout/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Serverless</guid>
      <dc:creator>Renato Losio</dc:creator>
      <dc:date>2026-09-19T09:11:00Z</dc:date>
      <dc:identifier>/news/2026/09/lambda-90-minute-timeout/en</dc:identifier>
    </item>
    <item>
      <title>Lambda SnapStart Comes to Container Images, Ending a Packaging Tradeoff</title>
      <link>https://www.infoq.com/news/2026/09/lambda-snapstart-container-image/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Serverless</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/09/lambda-snapstart-container-image/en/headerimage/generatedHeaderImage-1789052932475.jpg"/&gt;&lt;p&gt;AWS has extended Lambda SnapStart to container image functions, which hold up to 10 GB against 250 MB for zip archives. Teams previously chose between dependency headroom and sub-second startup. A Reddit thread from a month earlier shows what that cost: stripping whitespace and docstrings from installed packages to stay under the limit.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Serverless</category>
      <category>AWS Lambda</category>
      <category>Cloud</category>
      <category>AWS</category>
      <category>Containers</category>
      <category>Performance</category>
      <category>Architecture</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Sat, 12 Sep 2026 10:09:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/lambda-snapstart-container-image/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Serverless</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-09-12T10:09:00Z</dc:date>
      <dc:identifier>/news/2026/09/lambda-snapstart-container-image/en</dc:identifier>
    </item>
  </channel>
</rss>
