<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AWS on Alex's Blog</title><link>https://alexsun98.github.io/tags/aws/</link><description>Recent content in AWS on Alex's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://alexsun98.github.io/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>Cold starts, warm feelings: .NET APIs on AWS Lambda</title><link>https://alexsun98.github.io/posts/serverless-dotnet-lambda/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate><guid>https://alexsun98.github.io/posts/serverless-dotnet-lambda/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Sample post, here to fill out the list page and tag filters. Replace it
with your own writing.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The standard objection to .NET on Lambda is cold start time. It is a real
cost, but it is paid less often than people assume, and most of it can be
engineered away before you spend money on provisioned concurrency.&lt;/p&gt;
&lt;h2 id="where-cold-starts-actually-hurt"&gt;Where cold starts actually hurt&lt;/h2&gt;
&lt;p&gt;A cold start happens on the first request to a new execution environment.
For a steady-traffic API, that is a tiny fraction of requests. The places it
genuinely hurts:&lt;/p&gt;</description></item></channel></rss>