<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>API Gateway on PlumePHP</title><link>https://plumephp.com/tags/api-gateway/</link><description>Recent content in API Gateway on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Fri, 21 Nov 2025 10:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/api-gateway/index.xml" rel="self" type="application/rss+xml"/><item><title>微服务架构设计模式：API网关、服务发现与分布式通信实战指南</title><link>https://plumephp.com/microservices-design-patterns/</link><pubDate>Fri, 21 Nov 2025 10:00:00 +0800</pubDate><guid>https://plumephp.com/microservices-design-patterns/</guid><description>&lt;h2 id="引言"&gt;引言&lt;/h2&gt;
&lt;p&gt;微服务不是银弹。Martin Fowler 提出的&amp;quot;Microservice Premium&amp;quot;警示我们：微服务引入的分布式事务、服务发现、运维复杂度远超单体。更常见的是&amp;quot;Microservice Theater&amp;quot;——团队表面上拆分了几十个服务，实际上共用一个数据库、部署紧耦合、任何改动都需要跨团队协调。&lt;/p&gt;</description></item></channel></rss>