<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>服务治理 on PlumePHP</title><link>https://plumephp.com/tags/%E6%9C%8D%E5%8A%A1%E6%B2%BB%E7%90%86/</link><description>Recent content in 服务治理 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sat, 28 Dec 2024 10:18:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E6%9C%8D%E5%8A%A1%E6%B2%BB%E7%90%86/index.xml" rel="self" type="application/rss+xml"/><item><title>游戏服务器服务治理架构设计</title><link>https://plumephp.com/game-server-service-governance-architecture-design/</link><pubDate>Sat, 28 Dec 2024 10:18:00 +0800</pubDate><guid>https://plumephp.com/game-server-service-governance-architecture-design/</guid><description>&lt;p&gt;游戏服务器服务越来越多以后，真正困难的不是把服务跑起来，而是让服务之间的调用可控。网关调用角色服务，房间服调用结算服务，活动服务调用资产服务，后台任务调用邮件服务。任何一个下游变慢，都可能沿着调用链放大。服务治理架构的目标，是让调用有规则、故障有边界、发布有路径、排查有证据。&lt;/p&gt;</description></item></channel></rss>