<?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/%E9%99%90%E6%B5%81%E9%99%8D%E7%BA%A7/</link><description>Recent content in 限流降级 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Tue, 27 Sep 2022 22:08:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E9%99%90%E6%B5%81%E9%99%8D%E7%BA%A7/index.xml" rel="self" type="application/rss+xml"/><item><title>游戏服务器韧性架构模式</title><link>https://plumephp.com/game-server-resilience-patterns-architecture/</link><pubDate>Tue, 27 Sep 2022 22:08:00 +0800</pubDate><guid>https://plumephp.com/game-server-resilience-patterns-architecture/</guid><description>&lt;p&gt;游戏服务器最怕的不是某个服务偶尔失败，而是一个小失败被放大成全服故障。聊天服务慢了，网关线程被占满；排行榜缓存抖动，战斗结算也跟着超时；活动配置错误，所有玩家同时重试领取奖励。韧性架构的目标不是保证每个功能永不失败，而是让失败停在合理范围内，让核心体验优先活下来，让系统有时间恢复。&lt;/p&gt;</description></item></channel></rss>