[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-cross-service-consistency-zh-CN":3,"blog-related-cross-service-consistency-zh-CN":29,"blog-adjacent-cross-service-consistency-zh-CN":65},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":28},47,"cross-service-consistency","跨服务一致性：补偿比事务更现实","分布式事务听起来完备，实际项目中更常用的是可补偿的业务流程。","\u003Cp>当一次业务操作要同时写入订单系统、库存系统和财务系统时，强一致很难做到。我们的做法是先承认这一点，然后设计一套能够发现并修复不一致的机制。\u003C\u002Fp>\n\u003Ch2>三个务实原则\u003C\u002Fh2>\n\u003Cp>每一步都可追溯：记录操作时间、结果和请求号，出现不一致时能定位到具体环节。\u003C\u002Fp>\n\u003Cp>关键状态用最终一致：扣库存失败要能自动重试，重试失败进入人工处理队列。\u003C\u002Fp>\n\u003Cp>对账兜底：每天跑一次跨系统数据核对，发现差异自动生成工单，而不是等客户投诉。\u003C\u002Fp>\n\u003Ch2>一个真实例子\u003C\u002Fh2>\n\u003Cp>订单支付成功后调用库存服务超时，订单已置为已支付，库存却没有扣减。我们的处理是把库存变更写入消息，消费端幂等重试，超过阈值后告警。\u003C\u002Fp>\n\u003Cp>这套机制上线半年，自动修复了十几起不一致，没有一次需要人工介入。\u003C\u002Fp>\n\u003Cp>分布式系统一定会有短暂不一致。设计的目标不是永不出错，而是出错后能被发现并被修复。\u003C\u002Fp>","","indigo","佳益方圆团队","2026-03-27T10:41:00+08:00",1,false,[16,17,18],"分布式","一致性","架构",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},0,"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu","blue","article",60,{},[30,42,54],{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":41},30,"integration-api-pitfalls","企业系统集成：接口对接最容易踩的五个坑","接口文档写得再全，真正对接时仍然会卡在字段约定、超时和重复推送这些细节上。","cyan","2026-10-17T09:00:00+08:00",[38,39,40],"系统集成","接口","工程实践",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},{"id":13,"slug":43,"title":44,"excerpt":45,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":46,"updatedAt":47,"readingMinutes":48,"featured":49,"tags":50,"category":53},"why-enterprise-systems-age","为什么企业系统会在三年后开始“老化”","系统上线时功能齐全，三年后却处处别扭。问题往往不在代码，而在交付时被忽略的那些变化。","2026-10-16T09:30:00+08:00","2026-10-18T15:58:14.648+08:00",2,true,[51,52],"系统演进","架构设计",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},{"id":55,"slug":56,"title":57,"excerpt":58,"content":9,"cover":9,"tone":25,"author":11,"publishedAt":59,"updatedAt":59,"readingMinutes":13,"featured":14,"tags":60,"category":64},31,"idempotent-design-basics","幂等设计：重复提交不只是用户手抖","网络重试、消息重投、用户连点，都会让同一个请求到达多次。幂等应该设计在接口里。","2026-10-05T10:13:00+08:00",[61,62,63],"接口设计","幂等","可靠性",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},{"previous":66,"next":83},{"id":67,"slug":68,"title":69,"excerpt":70,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":71,"updatedAt":71,"readingMinutes":13,"featured":14,"tags":72,"category":76},26,"advice-to-small-teams","给刚起步团队的五条建议","如果重新开始一次，我们希望在第一天就知道这五件事。","2026-03-29T09:28:00+08:00",[73,74,75],"创业","建议","起步",{"id":77,"parentId":20,"slug":78,"name":79,"description":80,"icon":81,"cover":9,"tone":25,"kind":26,"sortOrder":82,"count":20},6,"founder-notes","创业手记","创始团队在经营、管理与产品上的思考，记录一家软件公司的成长过程。","pen-tool",10,{"id":84,"slug":85,"title":86,"excerpt":87,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":88,"updatedAt":88,"readingMinutes":13,"featured":14,"tags":89,"category":93},67,"pm-in-project-business","产品经理在项目制公司里做什么","没有独立产品线时，产品经理的价值不在画原型，而在替客户把问题想清楚。","2026-03-25T10:41:00+08:00",[90,91,92],"产品经理","项目制","角色",{"id":48,"parentId":20,"slug":94,"name":95,"description":96,"icon":97,"cover":9,"tone":25,"kind":26,"sortOrder":98,"count":20},"product-thinking","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb",50]