<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Docker on Jaehyun&#39;s Blog</title>
    <link>https://hongjae.pages.dev/en/tags/docker/</link>
    <description>Recent content in Docker on Jaehyun&#39;s Blog</description>
    <image>
      <title>Jaehyun&#39;s Blog</title>
      <url>https://pub-8eb6fdee382f4b0390e652016dc5f15a.r2.dev/og-image.jpg</url>
      <link>https://pub-8eb6fdee382f4b0390e652016dc5f15a.r2.dev/og-image.jpg</link>
    </image>
    <generator>Hugo -- 0.118.2</generator>
    <language>en</language>
    <lastBuildDate>Sat, 15 Jan 2022 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hongjae.pages.dev/en/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Much of AWS Should a Small Team Actually Use When Moving a Server?</title>
      <link>https://hongjae.pages.dev/en/posts/241120_aws_legacy_migration_pragmatic/</link>
      <pubDate>Sat, 15 Jan 2022 00:00:00 +0000</pubDate>
      <guid>https://hongjae.pages.dev/en/posts/241120_aws_legacy_migration_pragmatic/</guid>
      <description>When you need to move a legacy system to AWS or set up new infrastructure, searching for &amp;ldquo;AWS best practices&amp;rdquo; shows a lot of impressive architectures.
Things like EKS, multi-region setups, full Terraform modules, and service mesh.
Of course, those setups make total sense for big tech companies with huge traffic and dedicated infrastructure teams.
But in SI projects or smaller teams where I have mostly worked, the reality is very different.</description>
    </item>
  </channel>
</rss>
