<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud-Compute on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/cloud-compute/</link><description>Recent content in Cloud-Compute on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 13 Oct 2026 17:52:48 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/cloud-compute/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Lambda Web Functions adds HTTP-native serverless compute</title><link>https://curadevops.metacog.co.kr/insights/2026-10-13-aws-lambda-announces-lambda-web-functions/</link><pubDate>Tue, 13 Oct 2026 17:52:48 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-13-aws-lambda-announces-lambda-web-functions/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> New GA AWS Lambda primitive supporting direct HTTP handling (Express/Hono, no adapters) with a different billing model; worth tracking for future platform architecture patterns, but no existing infrastructure needs changing and existing Lambda Event Functions require no migration.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> The active-CPU billing model (vs. idle CPU) could meaningfully reduce Lambda costs for I/O-bound workloads; evaluate this as a golden-path serverless option and assess cost-optimization potential against current Lambda spend this planning cycle.&lt;/li>
&lt;/ul></description></item></channel></rss>