<?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/%E7%A4%BE%E4%BA%A4%E5%85%B3%E7%B3%BB/</link><description>Recent content in 社交关系 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sat, 14 Aug 2021 16:26:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E7%A4%BE%E4%BA%A4%E5%85%B3%E7%B3%BB/index.xml" rel="self" type="application/rss+xml"/><item><title>好友邀请一致性架构：申请、同意、拉黑和撤回如何不打架</title><link>https://plumephp.com/game-server-friend-invite-consistency-architecture/</link><pubDate>Sat, 14 Aug 2021 16:26:00 +0800</pubDate><guid>https://plumephp.com/game-server-friend-invite-consistency-architecture/</guid><description>&lt;h2 id="背景架构问题通常藏在正常路径之外"&gt;背景：架构问题通常藏在正常路径之外&lt;/h2&gt;
&lt;p&gt;好友系统看起来简单：A 申请，B 同意，两人成为好友。真实线上环境却有很多交叉动作：A 发申请后撤回，B 同时同意；B 拉黑 A 的瞬间，A 又发起组队邀请；两个人互相同时申请；客户端重试导致重复申请；跨区服玩家关系还要同步到多个读模型。好友邀请一致性架构要解决的是社交关系的单一事实来源和明确状态机。&lt;/p&gt;</description></item></channel></rss>