[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-peak-traffic-preparation-en":3,"blog-adjacent-peak-traffic-preparation-en":30,"blog-related-peak-traffic-preparation-en":67},{"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":29},86,"peak-traffic-preparation","Retrospective: Scaling Up the Night Before the Sale","The campaign page was load-tested, but login and coupons were what fell over.","\u003Cp>It was the client's first major online sale, with ten times normal traffic expected. We load-tested a week ahead. The first ten minutes went fine; at minute fifteen logins began failing.\u003C\u002Fp>\n\u003Ch2>Bottlenecks nobody predicted\u003C\u002Fh2>\n\u003Cp>Load tests covered product browsing, not login. When the sale started, every user signed in at once and the auth service became the limit.\u003C\u002Fp>\n\u003Cp>The coupon endpoint had no rate limit, so request volume exceeded database write capacity.\u003C\u002Fp>\n\u003Cp>Cache warm-up was incomplete; hot data went back to the database at the exact moment of peak pressure.\u003C\u002Fp>\n\u003Ch2>Our readiness checklist\u003C\u002Fh2>\n\u003Cp>Load tests cover the full chain: login, browse, order and payment, mixed in realistic proportions.\u003C\u002Fp>\n\u003Cp>Hot data is warmed before the event with staggered expiry times.\u003C\u002Fp>\n\u003Cp>Engineers are on site during the event, checking core metrics every fifteen minutes and degrading by plan if needed.\u003C\u002Fp>\n\u003Cp>Peak readiness is not about adding servers; it is knowing which link breaks first. Whatever the load test misses is where the risk lives.\u003C\u002Fp>","","teal","佳益方圆团队","2026-04-04T09:28:00+08:00",1,false,[16,17,18],"Retrospective","Peak Traffic","Performance",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},3,0,"project-retrospective","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","clipboard-check","blue","article",40,{},{"previous":31,"next":49},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":37,"updatedAt":37,"readingMinutes":13,"featured":14,"tags":38,"category":42},66,"docs-for-future-self","Write Product Docs for Your Future Self","Documentation is not a deliverable but team memory. Docs nobody reads are usually written for the wrong audience.","indigo","2026-04-06T09:28:00+08:00",[39,40,41],"Documentation","Team","Product",{"id":43,"parentId":21,"slug":44,"name":45,"description":46,"icon":47,"cover":9,"tone":26,"kind":27,"sortOrder":48,"count":21},2,"product-thinking","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","lightbulb",50,{"id":50,"slug":51,"title":52,"excerpt":53,"content":9,"cover":9,"tone":54,"author":11,"publishedAt":55,"updatedAt":55,"readingMinutes":13,"featured":14,"tags":56,"category":60},105,"team-offsite","Team Building Is Not Just Dinner","We ate many dinners and relationships did not improve. Now we work in the morning and play in the afternoon.","cyan","2026-04-02T09:28:00+08:00",[57,58,59],"Team Culture","Team Building","Atmosphere",{"id":61,"parentId":21,"slug":62,"name":63,"description":64,"icon":65,"cover":9,"tone":26,"kind":27,"sortOrder":66,"count":21},4,"team-culture","Team and Culture","Company events, tech sharing, team building and hiring culture that show the daily life of the Jiayifangyuan team.","users",30,[68,78,88],{"id":69,"slug":70,"title":71,"excerpt":72,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":73,"updatedAt":73,"readingMinutes":13,"featured":14,"tags":74,"category":77},70,"gov-project-acceptance","Retrospective: Why Acceptance Took Half a Year","The system was live for months while acceptance stalled. The causes were documents, process and communication, not software.","2026-10-13T09:00:00+08:00",[16,75,76],"Government","Acceptance",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":79,"slug":80,"title":81,"excerpt":82,"content":9,"cover":9,"tone":54,"author":11,"publishedAt":83,"updatedAt":83,"readingMinutes":13,"featured":14,"tags":84,"category":87},71,"mes-integration-retro","Retrospective: Integrating ERP With MES","The hard part of integration is not the interface, but getting two departments to agree on what a field means.","2026-10-01T10:13:00+08:00",[16,85,86],"Manufacturing","Integration",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":89,"slug":90,"title":91,"excerpt":92,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":93,"updatedAt":93,"readingMinutes":13,"featured":14,"tags":94,"category":97},72,"cross-border-site-retro","Retrospective: Traffic Arrived, Enquiries Did Not","Ads ran normally after launch but enquiries stayed low. The review found trust and form friction were the blockers.","2026-09-19T11:26:00+08:00",[16,95,96],"Cross-border","Conversion",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]