<?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/%E5%8F%91%E5%A5%96%E9%93%BE%E8%B7%AF/</link><description>Recent content in 发奖链路 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Fri, 09 Jun 2023 21:44:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E5%8F%91%E5%A5%96%E9%93%BE%E8%B7%AF/index.xml" rel="self" type="application/rss+xml"/><item><title>游戏奖励编排引擎架构设计</title><link>https://plumephp.com/game-server-reward-orchestration-engine-architecture/</link><pubDate>Fri, 09 Jun 2023 21:44:00 +0800</pubDate><guid>https://plumephp.com/game-server-reward-orchestration-engine-architecture/</guid><description>&lt;h2 id="问题背景"&gt;问题背景&lt;/h2&gt;
&lt;p&gt;奖励系统在项目早期常被当作工具函数：addItem、addGold、sendMail。等活动开始密集上线，问题就来了。战斗结算要立即发奖，运营补偿要批量发奖，任务领取要校验前置条件，礼包码要限制次数，邮件附件要延迟领取，平台退款还要回收资产。如果没有统一编排，团队会在每个入口重复处理幂等、限额、日志、资产变更和失败补偿。奖励编排引擎的定位是“把发奖变成一条可观察的业务流水线”。&lt;/p&gt;</description></item></channel></rss>