<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Docker on Puppeteers Oy</title>
		<link>https://www.puppeteers.net/tags/docker/</link>
		<description>Recent content in Docker on Puppeteers Oy</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Tue, 15 Jun 2021 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.puppeteers.net/tags/docker/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>To containerize in AWS or not: the cost perspective</title>
				<link>https://www.puppeteers.net/blog/to-containerize-in-aws-or-not-the-cost-perspective/</link>
				<pubDate>Tue, 15 Jun 2021 00:00:00 +0000</pubDate>
				<guid>https://www.puppeteers.net/blog/to-containerize-in-aws-or-not-the-cost-perspective/</guid>
				<description>&lt;p&gt;I recently checked the pricing model for &lt;a href=&#34;https://aws.amazon.com/fargate/?nc=sn&amp;amp;loc=1&amp;amp;whats-new-cards.sort-by=item.additionalFields.postDateTime&amp;amp;whats-new-cards.sort-order=desc&amp;amp;fargate-blogs.sort-by=item.additionalFields.createdDate&amp;amp;fargate-blogs.sort-order=desc&#34;&gt;Amazon Fargate&lt;/a&gt; to see if migrating a fair number of EC2 instance-based workloads to containers would save money. In theory this should have been the case, as a container has less &amp;ldquo;fat&amp;rdquo; compared to a full virtual machine. In this case the workload itself was perfectly suited for a container: a single process with single configuration file that was mostly network-bound running on t3.micro instances.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
