<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Ecs - Tag - IT Guy Journals</title>
        <link>https://www.itguyjournals.com/tags/ecs/</link>
        <description>Ecs - Tag - IT Guy Journals</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>luka.krapic@gmail.com (Luka Krapić)</managingEditor>
            <webMaster>luka.krapic@gmail.com (Luka Krapić)</webMaster><lastBuildDate>Fri, 02 May 2025 20:59:24 &#43;0100</lastBuildDate><atom:link href="https://www.itguyjournals.com/tags/ecs/" rel="self" type="application/rss+xml" /><item>
    <title>Building a Portable FastAPI Backend for AWS Lambda and ECS Using Terraform</title>
    <link>https://www.itguyjournals.com/building-fastapi-backend-for-aws-lambda-and-ecs-using-terraform/</link>
    <pubDate>Fri, 02 May 2025 20:59:24 &#43;0100</pubDate>
    <author>Luka Krapić</author>
    <guid>https://www.itguyjournals.com/building-fastapi-backend-for-aws-lambda-and-ecs-using-terraform/</guid>
    <description><![CDATA[<p>In the <a href="../building-backend-apis-with-fastapi-on-aws-lambda" rel="">previous post</a>, we explored how to deploy a FastAPI application on AWS Lambda using an ASGI adapter. This is a great option for early-stage projects: it requires zero infrastructure management, supports rapid iteration, and scales automatically.</p>
<p>But as your application matures, Lambda’s trade-offs can become limiting:</p>
<ul>
<li><strong>Cost scaling</strong> with consistent traffic</li>
<li><strong>Compute/memory coupling</strong> and lack of vertical scaling</li>
<li><strong>Package size limits</strong> and cold starts</li>
</ul>
<p>That’s why many teams adopt a container-based workflow that can run on both <strong>Lambda (via container images)</strong> and <strong>ECS Fargate</strong>. With a little planning, you can build once and deploy to either platform with minimal friction.</p>]]></description>
</item>
</channel>
</rss>
