<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Scalability on Fulgurion Systems Blog</title><link>https://fulgurion.com/blog/tags/scalability/</link><description>Recent content in Scalability on Fulgurion Systems Blog</description><image><title>Fulgurion Systems Blog</title><url>https://fulgurion.com/blog/images/Logo-linkedin.png</url><link>https://fulgurion.com/blog/images/Logo-linkedin.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 29 May 2026 00:00:00 -0300</lastBuildDate><atom:link href="https://fulgurion.com/blog/tags/scalability/index.xml" rel="self" type="application/rss+xml"/><item><title>Lambda Scales Automatically, but Within Limits</title><link>https://fulgurion.com/blog/posts/lambda-scales-within-limits/</link><pubDate>Fri, 29 May 2026 00:00:00 -0300</pubDate><guid>https://fulgurion.com/blog/posts/lambda-scales-within-limits/</guid><description>&lt;p&gt;Serverless is sold as a system that scales itself: you write the function, and as traffic grows AWS Lambda provisions whatever capacity it takes to keep up. That is true for the majority of workloads, and it is one of the better reasons to reach for Lambda. It is not unbounded. Lambda&amp;rsquo;s autoscaling is limited on two independent axes, and both are easy to miss until real traffic hits them:&lt;/p&gt;</description></item></channel></rss>