<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Docker - Tag - Misael Zapata</title><link>http://misael.org.s3-website-us-east-1.amazonaws.com/tags/docker/</link><description>Docker - Tag - Misael Zapata</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 09 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://misael.org.s3-website-us-east-1.amazonaws.com/tags/docker/" rel="self" type="application/rss+xml"/><item><title>fastfn Part 2: When a Function Isn't Enough (Services, Workloads, and the docker-compose I Didn't Want to Write)</title><link>http://misael.org.s3-website-us-east-1.amazonaws.com/fastfn-services-when-functions-arent-enough/</link><pubDate>Tue, 09 Jun 2026 00:00:00 +0000</pubDate><author><name>Misael Zapata</name></author><guid>http://misael.org.s3-website-us-east-1.amazonaws.com/fastfn-services-when-functions-arent-enough/</guid><description><![CDATA[<div class="featured-image">
                <img src="/fastfn-services-when-functions-arent-enough/images/cover.png" referrerpolicy="no-referrer">
            </div>Functions are a great shape for request/response. They&rsquo;re a terrible shape for a database. This is the part of fastfn where long-lived services joined the gateway — native docker, native process, Firecracker microVM — all behind one workload config.]]></description></item></channel></rss>