<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pothos on PlumePHP</title><link>https://plumephp.com/tags/pothos/</link><description>Recent content in Pothos 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/pothos/index.xml" rel="self" type="application/rss+xml"/><item><title>GraphQL 服务端实战：Apollo Server、GraphQL Yoga 与 Pothos 选型</title><link>https://plumephp.com/graphql-server-implementation/</link><pubDate>Thu, 13 Aug 2026 10:00:00 +0800</pubDate><guid>https://plumephp.com/graphql-server-implementation/</guid><description>&lt;p&gt;选型 GraphQL 服务端框架时，团队往往陷入&amp;quot;Apollo 一家独大是否最优&amp;quot;的思维惯性。本文聚焦 Node.js 生态中 Apollo Server、GraphQL Yoga 与 Pothos 三大代表性方案，从架构哲学、类型安全、插件生态、性能表现、学习曲线及维护活跃度六个维度展开硬核对比，并配以完整的 TypeScript 实战代码。无论你偏好 SDL-first 还是 Code-first，本文均有可直接落地的工程参考。&lt;/p&gt;</description></item></channel></rss>