<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fargate on LeanerCloud</title><link>https://leanercloud.com/tags/fargate.html</link><description>Recent content in Fargate on LeanerCloud</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 20 Aug 2026 02:08:40 +0200</lastBuildDate><atom:link href="https://leanercloud.com/tags/fargate/index.xml" rel="self" type="application/rss+xml"/><item><title>Moving bursty Fargate and EC2 workloads to Lambda for 10x savings</title><link>https://leanercloud.com/blog/2024-07-25-fargate-to-lambda-for-bursty-workloads.html</link><pubDate>Thu, 25 Jul 2024 19:04:45 +0000</pubDate><guid>https://leanercloud.com/blog/2024-07-25-fargate-to-lambda-for-bursty-workloads.html</guid><description>&lt;h2 id="fargate-is-not-always-the-cheapest-place-to-run-a-request"&gt;Fargate is not always the cheapest place to run a request&lt;/h2&gt;
&lt;p&gt;Fargate is a good default for containerized services, but for spiky web frontends and REST APIs it can be an expensive one. If your containers spend most of their time idle and then get slammed with requests for a few seconds at a time, you are paying for provisioned capacity that mostly sits waiting, and Fargate is often too slow to scale into the burst anyway, so users see latency spikes on top of the cost.&lt;/p&gt;</description></item></channel></rss>