[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-file-storage-evolution-en":3,"blog-adjacent-file-storage-evolution-en":29,"blog-related-file-storage-evolution-en":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},44,"file-storage-evolution","File Storage: From Local Disk to Object Storage","Attachment features start simple, until clients upload multi-gigabyte videos and ask for per-file permissions.","\u003Cp>Nearly every admin system has attachments. The first version stores files in a local directory and records a path in the database. That works fine for a single server, small files and few users.\u003C\u002Fp>\n\u003Ch2>When it has to change\u003C\u002Fh2>\n\u003Cp>With multiple servers, local directories are not shared, and a file uploaded in one request may be missing in the next.\u003C\u002Fp>\n\u003Cp>As volume grows, backup and migration costs climb and disk expansion becomes painful.\u003C\u002Fp>\n\u003Cp>Compliance requirements need fine-grained access control that a directory tree cannot express.\u003C\u002Fp>\n\u003Ch2>A migration path\u003C\u002Fh2>\n\u003Cp>Abstract a storage interface first, so business code depends on the interface rather than the filesystem.\u003C\u002Fp>\n\u003Cp>Write new uploads to object storage while legacy files stay at their paths and move gradually.\u003C\u002Fp>\n\u003Cp>Serve downloads through signed URLs with expiry and permission checks, so files cannot be scraped directly.\u003C\u002Fp>\n\u003Cp>Storage does not need to be perfect on day one, but the interface abstraction should exist from the start. Otherwise migration costs an order of magnitude more.\u003C\u002Fp>","","cyan","佳益方圆团队","2026-05-02T15:02:00+08:00",1,false,[16,17,18],"Storage","Architecture","Files",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},0,"engineering","Engineering","Hands-on engineering practices in architecture, performance optimization, AI integration and cross-platform delivery from our R and D team.","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},23,"how-small-teams-learn","How a Small Team Learns New Technology","No training budget, no study time. Learning has to be folded into real projects.","slate","2026-05-04T14:49:00+08:00",[38,39,40],"Startup","Technology","Learning",{"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","Founder Notes","Reflections from the founding team on business, management and product, documenting the growth of a software company.","pen-tool",10,{"id":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},64,"multilingual-product-costs","The Hidden Cost of a Multilingual Product","Translating the interface into English is only the beginning. The real cost sits in content, formats and business flows.","2026-04-30T15:02:00+08:00",[55,56,57],"Multilingual","Product","i18n",{"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","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","lightbulb",50,[66,76,86],{"id":67,"slug":68,"title":69,"excerpt":70,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":71,"updatedAt":71,"readingMinutes":13,"featured":14,"tags":72,"category":75},30,"integration-api-pitfalls","Five Traps in Enterprise System Integration","However complete the API documentation is, integration usually stalls on field semantics, timeouts and repeated pushes.","2026-10-17T09:00:00+08:00",[73,74,22],"Integration","APIs",{"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":77,"title":78,"excerpt":79,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":80,"updatedAt":81,"readingMinutes":59,"featured":82,"tags":83,"category":85},"why-enterprise-systems-age","Why Enterprise Systems Start to Age After Three Years","A system can pass acceptance with every feature checked, then feel awkward three years later. The problem is rarely the code — it is the changes that were never considered at delivery.","2026-10-16T09:30:00+08:00","2026-10-18T15:58:14.648+08:00",true,[84,17],"System Evolution",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},{"id":87,"slug":88,"title":89,"excerpt":90,"content":9,"cover":9,"tone":25,"author":11,"publishedAt":91,"updatedAt":91,"readingMinutes":13,"featured":14,"tags":92,"category":96},31,"idempotent-design-basics","Idempotency: Duplicate Submissions Are Not Just Double Clicks","Retries, redelivery and impatient users all send the same request more than once. Idempotency belongs in the API design.","2026-10-05T10:13:00+08:00",[93,94,95],"API Design","Idempotency","Reliability",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20}]