<?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/%E8%83%8C%E5%8C%85%E5%AE%B9%E9%87%8F/</link><description>Recent content in 背包容量 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Fri, 20 Aug 2021 12:19:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E8%83%8C%E5%8C%85%E5%AE%B9%E9%87%8F/index.xml" rel="self" type="application/rss+xml"/><item><title>批量奖励领取架构：一键领取背后的幂等、容量和补偿</title><link>https://plumephp.com/game-server-batch-reward-claim-architecture/</link><pubDate>Fri, 20 Aug 2021 12:19:00 +0800</pubDate><guid>https://plumephp.com/game-server-batch-reward-claim-architecture/</guid><description>&lt;h2 id="背景架构问题通常藏在正常路径之外"&gt;背景：架构问题通常藏在正常路径之外&lt;/h2&gt;
&lt;p&gt;玩家点击“一键领取”时，背后可能包含十几个任务奖励、活动奖励、邮件附件和通行证节点。每个奖励来源都有自己的状态和限制：任务是否完成，邮件是否过期，背包是否有空间，货币是否到上限，活动是否仍在开放。批量奖励领取架构要让这个动作既方便玩家，又不把服务端拖进一团跨系统事务。&lt;/p&gt;</description></item></channel></rss>