<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lambda on Teddy Ferdinand</title><link>https://tferdinand.net/en/tags/lambda/</link><description>Recent content in Lambda on Teddy Ferdinand</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 27 Apr 2020 06:01:08 +0000</lastBuildDate><atom:link href="https://tferdinand.net/en/tags/lambda/index.xml" rel="self" type="application/rss+xml"/><item><title>Accelerate the test of your lambda functions with Docker</title><link>https://tferdinand.net/en/accelerate-the-test-of-your-lambda-functions-with-docker/</link><pubDate>Mon, 27 Apr 2020 06:00:00 +0000</pubDate><guid>https://tferdinand.net/en/accelerate-the-test-of-your-lambda-functions-with-docker/</guid><description>&lt;p&gt;Lambda is a very powerful AWS tool. Executing scripts in serverless mode drastically reduces the cost and complexity of managing a scalable infrastructure, however, testing its functions directly on Lambda can sometimes be frustrating as it requires round trips between the development station and the AWS environment.&lt;/p&gt;
&lt;p&gt;There are testing features built into the AWS toolkit for the most popular editors (&lt;a href="https://aws.amazon.com/visualstudiocode/"&gt;for Microsoft Visual Studio Code&lt;/a&gt; / &lt;a href="https://aws.amazon.com/pycharm/"&gt;PyCharm&lt;/a&gt;, for example), however, this restricts the possible editors and creates an adherence that is not particularly desirable.&lt;/p&gt;</description></item></channel></rss>