<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Runtime on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/runtime/</link><description>Recent content in Runtime on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 26 Aug 2026 11:21:00 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/runtime/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Lambda public preview: managed runtimes for Node.js 26 and Python 3.15</title><link>https://curadevops.metacog.co.kr/insights/2026-08-26-aws-lambda-introduces-managed-runtimes-in-public-preview-for/</link><pubDate>Wed, 26 Aug 2026 11:21:00 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-26-aws-lambda-introduces-managed-runtimes-in-public-preview-for/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> AWS&amp;rsquo;s new preview model lets platform teams validate Lambda workloads against upcoming runtimes before GA; pre-GA and explicitly unsupported for production, so evaluate only in non-critical environments.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> Notable design detail: preview runtimes use the same identifier as the eventual GA release, so Lambda functions automatically graduate with no pipeline or IaC changes required — worth factoring into future Lambda deployment workflows once GA.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> pre-GA (alpha/beta/RC/preview) · breaking-change flagged&lt;/li>
&lt;/ul></description></item></channel></rss>