<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Marcos Davila on Medium]]></title>
        <description><![CDATA[Stories by Marcos Davila on Medium]]></description>
        <link>https://medium.com/@marcos.duarte242?source=rss-194af9ca810f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Xadv1Ku_AIiZAVvGU9n7OQ.jpeg</url>
            <title>Stories by Marcos Davila on Medium</title>
            <link>https://medium.com/@marcos.duarte242?source=rss-194af9ca810f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:58:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marcos.duarte242/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Keeping Your AWS Lambdas Warm: Strategies to Avoid Cold Starts]]></title>
            <link>https://medium.com/@marcos.duarte242/keeping-your-aws-lambdas-warm-strategies-to-avoid-cold-starts-c3b50a001a6c?source=rss-194af9ca810f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3b50a001a6c</guid>
            <category><![CDATA[serverless-architecture]]></category>
            <category><![CDATA[cold-start]]></category>
            <category><![CDATA[lambda]]></category>
            <category><![CDATA[warm-up]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Marcos Davila]]></dc:creator>
            <pubDate>Mon, 06 Nov 2023 10:56:55 GMT</pubDate>
            <atom:updated>2023-11-06T10:56:55.416Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p_v1H-aVkqKrx-eiiT7emQ.jpeg" /><figcaption>Image by chess.com</figcaption></figure><p>In the world of cloud computing and serverless architecture, AWS Lambdas have become a fundamental piece of the puzzle. They are fast, scalable, and cost-effective, but they often face a challenge known as a “cold start.” A cold start refers to the time it takes to initialize a Lambda when it receives a request, which can lead to a slow user experience and impact application efficiency. In this article, we’ll explore how to keep Lambdas “warm” and avoid the dreaded cold starts.</p><h3>The Cold Start Dilemma</h3><p>When a Lambda is first triggered or hasn’t been used for a while, AWS needs to create a new container to run it. This can result in slower response times, which is unacceptable in real-time or critical applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2uZkyqiwd5kU9QTst-rJyA.png" /><figcaption>Image by AWS re:Invent 2021</figcaption></figure><h3>Personal Experience</h3><p>To understand the importance of this issue, let me share my own experience. In a critical environment like the banking sector, service requests must be handled in under 1.5 seconds. Initially, cold starts were a significant hurdle that seriously impacted our response times.</p><p>However, by implementing a rule in EventBridge, we achieved a substantial improvement. We configured EventBridge to send mock requests to critical services at regular intervals. This kept the containers of the Lambdas active and dramatically reduced response times. Now, our services operate with response times ranging from 200 to 400 milliseconds, resulting in a significantly faster, more efficient, and risk-free user experience in the banking sector.</p><h3>Strategies for Keeping Lambdas Warm</h3><ol><li>EventBridge Rule: An effective way to keep Lambdas warm is to create an EventBridge rule that sends dummy requests to the Lambdas at regular intervals. This ensures that containers remain active and ready to respond to real requests. This strategy was pivotal in our banking experience and can be applied to various use cases.</li><li>Provisioned Concurrency: AWS offers the “provisioned concurrency” feature, which allows you to set the number of pre-configured Lambda containers that will be kept warm. While this option guarantees consistent performance, it should be carefully considered as it comes with additional costs.</li><li>Serverless WarmUp Plugin: Another intriguing solution is the use of the “Serverless WarmUp” plugin, which creates a scheduled Lambda that invokes all selected Lambdas in a configured time interval. This forces your Lambda containers to stay active and warm.</li></ol><h3>Conclusion</h3><p>In conclusion, cold starts are a common challenge in the world of AWS Lambdas, but effective strategies exist to keep your Lambdas warm and prevent delays in requests. We have firsthand experience of how implementing an EventBridge rule can make a difference, especially in a critical environment.</p><p>Additionally, options such as provisioned concurrency and using the Serverless WarmUp Plugin can be helpful to ensure consistent performance, though you must consider associated costs.</p><p>Keeping Lambdas warm is essential to ensure an optimal and efficient user experience in your serverless applications. Don’t let cold starts affect user satisfaction and application efficiency!</p><p>Enjoy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3b50a001a6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>