<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>containers on Grahams Blog</title><link>https://6621eb77.personal-website-9uy.pages.dev/blog/tags/containers/</link><description>Recent content in containers on Grahams Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© Graham Hughes</copyright><lastBuildDate>Sat, 30 Mar 2024 13:49:14 -0400</lastBuildDate><atom:link href="https://6621eb77.personal-website-9uy.pages.dev/blog/tags/containers/index.xml" rel="self" type="application/rss+xml"/><item><title>5x Decrease In Build Time For AWS Lambda</title><link>https://6621eb77.personal-website-9uy.pages.dev/blog/posts/5x_decrease_in_build_time_for_aws_lambda/</link><pubDate>Sat, 30 Mar 2024 13:49:14 -0400</pubDate><guid>https://6621eb77.personal-website-9uy.pages.dev/blog/posts/5x_decrease_in_build_time_for_aws_lambda/</guid><description>Background: At my work we have an API that is setup as an AWS API gateway with Lambda functions attached to the API gateway routes. We package the Lambda functions in containers. This blog post goes over the benefits of packaging your Lambdas in containers. Pretty standard setup. Each Lambda function had its own Python file and Dockerfile. At the time of writing there are around ~15 unique Lambda functions. The project file structure was as follows.</description></item></channel></rss>