<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Traefik on PlumePHP</title><link>https://plumephp.com/tags/traefik/</link><description>Recent content in Traefik on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Thu, 13 Aug 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/traefik/index.xml" rel="self" type="application/rss+xml"/><item><title>API 网关实战：Kong、Envoy 与 Traefik 选型与部署</title><link>https://plumephp.com/api-gateway-kong-envoy/</link><pubDate>Thu, 13 Aug 2026 10:00:00 +0800</pubDate><guid>https://plumephp.com/api-gateway-kong-envoy/</guid><description>&lt;p&gt;API 网关是微服务架构的流量入口与治理中枢。面对 Kong、Envoy、Traefik 三条技术路径，团队常陷入&amp;quot;功能相似、生态重叠、指标不透明&amp;quot;的选型困境。本文从架构原理、14 维度横向对比、三大网关深度实战三个层面，系统梳理 API 网关的技术全景，并给出可直接落地的生产配置。&lt;/p&gt;</description></item></channel></rss>