[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-integration-api-pitfalls-zh-CN":3,"blog-adjacent-integration-api-pitfalls-zh-CN":29,"blog-related-integration-api-pitfalls-zh-CN":42},{"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},30,"integration-api-pitfalls","企业系统集成：接口对接最容易踩的五个坑","接口文档写得再全，真正对接时仍然会卡在字段约定、超时和重复推送这些细节上。","\u003Cp>过去几年我们做了不少系统集成项目，对接过 ERP、MES、财务软件和各种 SaaS。几乎每个项目都会在某个看起来简单的接口上卡住两三天。下面五个坑出现频率最高。\u003C\u002Fp>\n\u003Ch2>五个高频问题\u003C\u002Fh2>\n\u003Cp>一、字段含义不一致。对方叫“订单号”，实际是同一天的流水号，重号天天出现。对接前必须逐字段确认语义，而不是只看名字。\u003C\u002Fp>\n\u003Cp>二、时间格式和时区。对方返回本地时间字符串，我们按 UTC 解析，数据整体偏移八小时。\u003C\u002Fp>\n\u003Cp>三、超时与重试。对方接口平均响应三秒，我们默认五秒超时，高峰期大量失败，重试又造成重复写入。\u003C\u002Fp>\n\u003Cp>四、重复推送。对方开启补偿机制，同一条记录可能推三次，没有幂等键就会产生脏数据。\u003C\u002Fp>\n\u003Cp>五、状态码不统一。成功返回 200，业务失败也返回 200，只看 HTTP 状态会漏掉一半错误。\u003C\u002Fp>\n\u003Ch2>我们的对接清单\u003C\u002Fh2>\n\u003Cp>每次对接先做一份字段映射表，中文含义、类型、取值范围、是否必填全部列清，双方签字确认。\u003C\u002Fp>\n\u003Cp>在联调环境模拟三类异常：超时、重复、部分成功。这三类跑通，上线才比较安心。\u003C\u002Fp>\n\u003Cp>集成项目的成败往往不取决于技术难度，而取决于双方对同一句话的理解是否一致。\u003C\u002Fp>","","cyan","佳益方圆团队","2026-10-17T09:00: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":-1,"next":30},{"id":13,"slug":31,"title":32,"excerpt":33,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":34,"updatedAt":35,"readingMinutes":36,"featured":37,"tags":38,"category":41},"why-enterprise-systems-age","为什么企业系统会在三年后开始“老化”","系统上线时功能齐全，三年后却处处别扭。问题往往不在代码，而在交付时被忽略的那些变化。","2026-10-16T09:30:00+08:00","2026-10-18T15:58:14.648+08:00",2,true,[39,40],"系统演进","架构设计",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},[43,46,57],{"id":13,"slug":31,"title":32,"excerpt":33,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":34,"updatedAt":35,"readingMinutes":36,"featured":37,"tags":44,"category":45},[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":47,"slug":48,"title":49,"excerpt":50,"content":9,"cover":9,"tone":25,"author":11,"publishedAt":51,"updatedAt":51,"readingMinutes":13,"featured":14,"tags":52,"category":56},31,"idempotent-design-basics","幂等设计：重复提交不只是用户手抖","网络重试、消息重投、用户连点，都会让同一个请求到达多次。幂等应该设计在接口里。","2026-10-05T10:13:00+08:00",[53,54,55],"接口设计","幂等","可靠性",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},{"id":58,"slug":59,"title":60,"excerpt":61,"content":9,"cover":9,"tone":25,"author":11,"publishedAt":62,"updatedAt":63,"readingMinutes":36,"featured":14,"tags":64,"category":67},3,"miniapp-or-app","小程序还是 App？先看业务发生在什么场景","技术偏好不该成为选型依据。低频与高频、分享与留存、能力边界，才是决定载体的关键。","2026-09-25T09:00:00+08:00","2026-10-18T15:58:14.677+08:00",[65,66],"移动端","技术选型",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20}]