[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-message-queue-tradeoffs-zh-CN":3,"blog-adjacent-message-queue-tradeoffs-zh-CN":29,"blog-related-message-queue-tradeoffs-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},38,"message-queue-tradeoffs","消息队列不是万能药","引入队列能解决耦合和削峰，也会带来重复、顺序和可观测性三类新问题。","\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>\n\u003Cp>队列是工具，不是架构目标。能用一次同步调用解决的事情，就别增加一个中间件。\u003C\u002Fp>","","teal","佳益方圆团队","2026-07-13T09:44: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,{},{"previous":30,"next":48},{"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},17,"hiring-is-harder-than-sales","招人比接单更难","客户可以慢慢挑，人却必须在有限的时间里做判断。我们踩过的坑大多和招人有关。","slate","2026-07-15T16:31:00+08:00",[38,39,40],"创业","招聘","团队",{"id":42,"parentId":20,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":25,"kind":26,"sortOrder":47,"count":20},6,"founder-notes","创业手记","创始团队在经营、管理与产品上的思考，记录一家软件公司的成长过程。","pen-tool",10,{"id":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},58,"dashboard-metric-definition","看板指标：先定义再看数","同一个“客户数”，销售、财务和运营的理解可能完全不同。","2026-07-11T09:44:00+08:00",[55,56,57],"数据看板","指标","产品设计",{"id":59,"parentId":20,"slug":60,"name":61,"description":62,"icon":63,"cover":9,"tone":25,"kind":26,"sortOrder":64,"count":20},2,"product-thinking","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb",50,[66,77,88],{"id":67,"slug":68,"title":69,"excerpt":70,"content":9,"cover":9,"tone":71,"author":11,"publishedAt":72,"updatedAt":72,"readingMinutes":13,"featured":14,"tags":73,"category":76},30,"integration-api-pitfalls","企业系统集成：接口对接最容易踩的五个坑","接口文档写得再全，真正对接时仍然会卡在字段约定、超时和重复推送这些细节上。","cyan","2026-10-17T09:00:00+08:00",[74,75,18],"系统集成","接口",{"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":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":71,"author":11,"publishedAt":81,"updatedAt":82,"readingMinutes":59,"featured":83,"tags":84,"category":87},"why-enterprise-systems-age","为什么企业系统会在三年后开始“老化”","系统上线时功能齐全，三年后却处处别扭。问题往往不在代码，而在交付时被忽略的那些变化。","2026-10-16T09:30:00+08:00","2026-10-18T15:58:14.648+08:00",true,[85,86],"系统演进","架构设计",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},{"id":89,"slug":90,"title":91,"excerpt":92,"content":9,"cover":9,"tone":25,"author":11,"publishedAt":93,"updatedAt":93,"readingMinutes":13,"featured":14,"tags":94,"category":98},31,"idempotent-design-basics","幂等设计：重复提交不只是用户手抖","网络重试、消息重投、用户连点，都会让同一个请求到达多次。幂等应该设计在接口里。","2026-10-05T10:13:00+08:00",[95,96,97],"接口设计","幂等","可靠性",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20}]