
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sat, 16 May 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/traefik/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-api-gateway-2026-kong-tyk-apigee-krakend-zuplo-envoy-gateway-traefik-3-deep-dive.en</guid>
    <title>API Gateways in 2026 — Kong 4 / Tyk / Apigee / KrakenD / Zuplo / Envoy Gateway / Traefik 3 Deep Dive (15 Options, 4 Categories)</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-api-gateway-2026-kong-tyk-apigee-krakend-zuplo-envoy-gateway-traefik-3-deep-dive.en</link>
    <description>In 2026, the API gateway market splits four ways — open-source self-hosted (Kong 4, Tyk, KrakenD, Envoy Gateway, Traefik 3, Gravitee), managed SaaS/cloud (Apigee, AWS API Gateway, Cloudflare API Gateway, Azure API Management, MuleSoft), programmable edge (Zuplo), and the newly emerged LLM API gateways (Portkey, Helicone, OpenRouter). Mashery was sunset January 2024, Kong doubled down on Konnect cloud, and Envoy Gateway graduated from CNCF. This piece compares 15 options by category, features, pricing, and real-world usage — Toss internal gateway, Kakao API platform, Mercari and ZOZO microservices. Rate limiting, auth, schema validation, caching, BFF patterns, OpenAPI 3.1 and AsyncAPI 2/3, gRPC and WebSocket support, and how gateways get redefined in the LLM era.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>api-gateway</category><category>kong</category><category>tyk</category><category>apigee</category><category>krakend</category><category>zuplo</category><category>aws-api-gateway</category><category>cloudflare-api</category><category>azure-apim</category><category>gravitee</category><category>envoy-gateway</category><category>traefik</category><category>portkey</category><category>helicone</category><category>openrouter</category><category>2026</category><category>deep-dive</category><category>english</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-api-gateway-2026-kong-tyk-apigee-krakend-zuplo-envoy-gateway-traefik-3-deep-dive.ja</guid>
    <title>2026年のAPIゲートウェイ — Kong 4 / Tyk / Apigee / KrakenD / Zuplo / Envoy Gateway / Traefik 3 徹底比較(15選・4カテゴリ)</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-api-gateway-2026-kong-tyk-apigee-krakend-zuplo-envoy-gateway-traefik-3-deep-dive.ja</link>
    <description>2026年のAPIゲートウェイ市場は4つに分かれた — オープンソースのセルフホスト(Kong 4, Tyk, KrakenD, Envoy Gateway, Traefik 3, Gravitee)、マネージドSaaS/クラウド(Apigee, AWS API Gateway, Cloudflare API Gateway, Azure API Management, MuleSoft)、プログラマブルなエッジ(Zuplo)、そして新興のLLM APIゲートウェイ(Portkey, Helicone, OpenRouter)。Masheryは2024年1月にサンセット、KongはKonnectでクラウド側を強化、Envoy GatewayはCNCF Graduatedに昇格。この記事では15の選択肢をカテゴリ・機能・価格・実例で比較する — Tossの自家製ゲートウェイ、KakaoのAPIプラットフォーム、メルカリ・ZOZOのマイクロサービスまで。レート制限・認証・スキーマ検証・キャッシュ・BFFパターン、OpenAPI 3.1とAsyncAPI 2/3、gRPC・WebSocketサポート、そしてLLM時代にゲートウェイがどう再定義されるか。</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>api-gateway</category><category>kong</category><category>tyk</category><category>apigee</category><category>krakend</category><category>zuplo</category><category>aws-api-gateway</category><category>cloudflare-api</category><category>azure-apim</category><category>gravitee</category><category>envoy-gateway</category><category>traefik</category><category>portkey</category><category>helicone</category><category>openrouter</category><category>2026</category><category>deep-dive</category><category>日本語</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-api-gateway-2026-kong-tyk-apigee-krakend-zuplo-envoy-gateway-traefik-3-deep-dive</guid>
    <title>API 게이트웨이 2026 — Kong 4 / Tyk / Apigee / KrakenD / Zuplo / Envoy Gateway / Traefik 3 심층 비교 (15가지 옵션, 4가지 분류)</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-api-gateway-2026-kong-tyk-apigee-krakend-zuplo-envoy-gateway-traefik-3-deep-dive</link>
    <description>2026년 현재 API 게이트웨이 시장은 네 갈래로 갈라졌다 — 오픈소스 셀프호스팅(Kong 4, Tyk, KrakenD, Envoy Gateway, Traefik 3, Gravitee), 매니지드 SaaS/클라우드(Apigee, AWS API Gateway, Cloudflare API Gateway, Azure API Management, MuleSoft), 프로그래머블 엣지(Zuplo), 그리고 새롭게 떠오른 LLM API 게이트웨이(Portkey, Helicone, OpenRouter). Mashery는 2024년 1월에 일몰됐고, Kong은 Konnect로 클라우드를 강화했으며, Envoy Gateway는 CNCF Graduated로 올라갔다. 이 글은 15가지 옵션을 분류·기능·가격·실제 사용 사례로 비교한다 — 토스의 자체 게이트웨이, 카카오의 API 플랫폼, Mercari·ZOZO의 마이크로서비스 진영까지. rate limiting·인증·schema validation·caching·BFF 패턴, OpenAPI 3.1과 AsyncAPI 2/3, gRPC·WebSocket 지원, 그리고 LLM 시대에 게이트웨이가 어떻게 재정의되는지.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>api-gateway</category><category>kong</category><category>tyk</category><category>apigee</category><category>krakend</category><category>zuplo</category><category>aws-api-gateway</category><category>cloudflare-api</category><category>azure-apim</category><category>gravitee</category><category>envoy-gateway</category><category>traefik</category><category>portkey</category><category>helicone</category><category>openrouter</category><category>2026</category><category>deep-dive</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-reverse-proxy-edge-servers-2026-nginx-caddy-traefik-haproxy-envoy-openresty-pingora-frankenphp-deep-dive.en</guid>
    <title>Reverse Proxy &amp; Edge Servers 2026 Complete Guide — nginx · Caddy · Traefik · HAProxy · Envoy · OpenResty · Pingora · FrankenPHP Deep Dive</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-reverse-proxy-edge-servers-2026-nginx-caddy-traefik-haproxy-envoy-openresty-pingora-frankenphp-deep-dive.en</link>
    <description>Full-stack anatomy of reverse proxies and edge servers in 2026. nginx 1.27 and the freenginx fork drama, Caddy 2.8 automatic HTTPS, Traefik 3 dynamic routing, HAProxy 3.x L4/L7, Envoy 1.32 service mesh data plane, OpenResty Lua, Cloudflare Pingora Rust rewrite serving trillions of requests, FrankenPHP inside Caddy, K8s Ingress and Gateway API, Cloudflare Workers · Fastly Compute · Vercel Edge · Netlify Edge · Lambda@Edge · CloudFront Functions, mTLS · ACME · HTTP/3 QUIC, ModSecurity and Coraza WAF, NAVER · Kakao · NHN · NTT · SAKURA adoption. Decision matrix included.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>reverse-proxy</category><category>nginx</category><category>caddy</category><category>traefik</category><category>haproxy</category><category>envoy</category><category>openresty</category><category>pingora</category><category>frankenphp</category><category>load-balancer</category><category>edge</category><category>english</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-reverse-proxy-edge-servers-2026-nginx-caddy-traefik-haproxy-envoy-openresty-pingora-frankenphp-deep-dive.ja</guid>
    <title>リバースプロキシ &amp; エッジサーバー 2026 完全ガイド - nginx · Caddy · Traefik · HAProxy · Envoy · OpenResty · Pingora · FrankenPHP 徹底解剖</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-reverse-proxy-edge-servers-2026-nginx-caddy-traefik-haproxy-envoy-openresty-pingora-frankenphp-deep-dive.ja</link>
    <description>2026年のリバースプロキシとエッジサーバーをフルスタックで解剖。nginx 1.27 と freenginx フォーク騒動、Caddy 2.8 の自動 HTTPS、Traefik 3 の動的ルーティング、HAProxy 3.x の L4/L7、Envoy 1.32 サービスメッシュデータプレーン、OpenResty Lua、Cloudflare Pingora の Rust 書き直し（日数兆リクエスト処理）、FrankenPHP、K8s Ingress と Gateway API、Cloudflare Workers · Fastly Compute · Vercel Edge · Netlify Edge · Lambda@Edge · CloudFront Functions、mTLS · ACME · HTTP/3 QUIC、ModSecurity と Coraza WAF、NAVER · Kakao · NHN · NTT · SAKURA の韓日採用事例まで。意思決定マトリックス付き。</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>reverse-proxy</category><category>nginx</category><category>caddy</category><category>traefik</category><category>haproxy</category><category>envoy</category><category>openresty</category><category>pingora</category><category>frankenphp</category><category>load-balancer</category><category>edge</category><category>日本語</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-05-16-reverse-proxy-edge-servers-2026-nginx-caddy-traefik-haproxy-envoy-openresty-pingora-frankenphp-deep-dive</guid>
    <title>리버스 프록시 &amp; 엣지 서버 2026 완벽 가이드 - nginx · Caddy · Traefik · HAProxy · Envoy · OpenResty · Pingora · FrankenPHP 심층 분석</title>
    <link>https://www.youngju.dev/blog/culture/2026-05-16-reverse-proxy-edge-servers-2026-nginx-caddy-traefik-haproxy-envoy-openresty-pingora-frankenphp-deep-dive</link>
    <description>2026년 리버스 프록시와 엣지 서버 풀스택 해부. nginx 1.27과 freenginx 포크 드라마, Caddy 2.8의 자동 HTTPS, Traefik 3의 동적 라우팅, HAProxy 3.x의 L4/L7, Envoy 1.32 서비스 메시, OpenResty Lua, Cloudflare Pingora의 Rust 리라이트, FrankenPHP, K8s Ingress와 Gateway API, Cloudflare Workers · Fastly Compute · Vercel Edge · Netlify Edge · Lambda@Edge · CloudFront Functions, mTLS · ACME · HTTP/3 QUIC, ModSecurity와 Coraza WAF, NAVER · Kakao · NHN · NTT · SAKURA 한일 사례까지. 의사결정 매트릭스 포함.</description>
    <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>reverse-proxy</category><category>nginx</category><category>caddy</category><category>traefik</category><category>haproxy</category><category>envoy</category><category>openresty</category><category>pingora</category><category>frankenphp</category><category>load-balancer</category><category>edge</category>
  </item>

    </channel>
  </rss>
