[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-GnqtM2MqYK50Np8zeJEbxGDTce70u2WlF6_FoWiAS7Y":3,"sanity-zVsHmv4U4Sp4jckbBBNRDDUPH31Ezy2KTbh0G_q0ux0":252},{"data":4,"sourceMap":-1},{"latestPodcast":5,"latestReleases":14,"post":39,"recent":227},[6],{"_id":7,"publishedAt":8,"slug":9,"sponsored":12,"title":13},"7ebd76d2-cebc-4b88-82f9-3dfb2c8bc5ca","2026-07-08T04:40:00.000Z",{"_type":10,"current":11},"slug","what-s-left-for-infrastructure-as-code-after-ai-moves-in",true,"What's left for infrastructure-as-code after AI moves in?",[15,21,27,33],{"_id":16,"publishedAt":17,"slug":18,"title":20},"eb5b66eb-9410-4329-83bb-22bbff39402a","2026-04-28T13:00:00.000Z",{"_type":10,"current":19},"turn-scattered-knowledge-into-trusted-intelligence","Turning scattered knowledge into trusted intelligence: Stack Internal 2026.3",{"_id":22,"publishedAt":23,"slug":24,"title":26},"369c2401-b62e-4a37-8ff8-bf603023ecad","2026-03-02T15:03:00.988Z",{"_type":10,"current":25},"what-s-new-at-stack-overflow-march-2026","What’s new at Stack Overflow: March 2026",{"_id":28,"publishedAt":29,"slug":30,"title":32},"5e9053a4-07ea-447c-91ea-29e0b6228537","2026-02-02T15:00:00.000Z",{"_type":10,"current":31},"what-s-new-at-stack-overflow-february-2026","What’s new at Stack Overflow: February 2026",{"_id":34,"publishedAt":35,"slug":36,"title":38},"a1b538eb-a8a6-46d0-80a1-ac70ec9bb935","2026-01-05T10:00:00.000-05:00",{"_type":10,"current":37},"what-s-new-at-stack-overflow-january-2026","What’s new at Stack Overflow: January 2026",{"_createdAt":40,"_id":41,"_rev":42,"_type":43,"_updatedAt":44,"author":45,"body":59,"comments":12,"dateUrl":199,"excerpt":200,"legacyBody":201,"product":82,"publishedAt":204,"slug":205,"sponsored":82,"tags":207,"title":226,"visible":12},"2023-05-25T09:36:59Z","wp-post-3524","07ZbrKPSUrjrV4wQ6fICJv","blogPost","2023-07-13T14:54:26Z",[46],{"_createdAt":47,"_id":48,"_rev":49,"_type":50,"_updatedAt":51,"avatar":52,"employee":54,"name":55,"role":56,"slug":57},"2023-05-23T16:27:18Z","wp-author-114","07ZbrKPSUrjrV4wQ6fam8u","blogAuthor","2023-08-29T11:49:01Z",{"_type":53},"image","former","Jeff Atwood","Co-founder",{"current":58},"jeffatwood",[60,84,103,131,149,158,173],{"_key":61,"_type":62,"children":63,"markDefs":78,"style":83},"01ca0adc79dc","block",[64,69,74],{"_key":65,"_type":66,"marks":67,"text":68},"01ca0adc79dc0","span",[],"It was quite an honor to see that the ",{"_key":70,"_type":66,"marks":71,"text":73},"01ca0adc79dc1",[72],"a81a21e3a60c","High Scalability Blog posted an entry on Stack Overflow",{"_key":75,"_type":66,"marks":76,"text":77},"01ca0adc79dc2",[],"!",[79],{"_key":72,"_type":80,"href":81,"reference":82},"link","http:\u002F\u002Fhighscalability.com\u002Fstack-overflow-architecture",null,"normal",{"_key":85,"_type":62,"children":86,"markDefs":100,"style":83},"e4f87484931d",[87,91,96],{"_key":88,"_type":66,"marks":89,"text":90},"e4f87484931d0",[],"We referred to the HSB, and its exhaustively detailed information about how other websites handle scaling, many times during the course of Stack Overflow development. And I've ",{"_key":92,"_type":66,"marks":93,"text":95},"e4f87484931d1",[94],"2a2c6a9c519c","cited it myself",{"_key":97,"_type":66,"marks":98,"text":99},"e4f87484931d2",[]," when researching what we think is the largest public same-stack (Microsoft) website on the internet, Plenty of Fish. It's an excellent resource.",[101],{"_key":94,"_type":80,"href":102,"reference":82},"http:\u002F\u002Fwww.codinghorror.com\u002Fblog\u002Farchives\u002F001195.html",{"_key":104,"_type":62,"children":105,"markDefs":128,"style":83},"b816cf3d53dd",[106,110,115,119,124],{"_key":107,"_type":66,"marks":108,"text":109},"b816cf3d53dd0",[],"I don't know if Stack Overflow has ",{"_key":111,"_type":66,"marks":112,"text":114},"b816cf3d53dd1",[113],"em","that",{"_key":116,"_type":66,"marks":117,"text":118},"b816cf3d53dd2",[]," much traffic relative to many of the other truly giant public websites profiled on the HSB. You can see ",{"_key":120,"_type":66,"marks":121,"text":123},"b816cf3d53dd3",[122],"6e77b5014719","our public Stack Overflow traffic stats at Quantcast",{"_key":125,"_type":66,"marks":126,"text":127},"b816cf3d53dd4",[]," if you're curious. Still, it's great to be able to give back to the community and help document our own process of scaling our little corner of the web.",[129],{"_key":122,"_type":80,"href":130,"reference":82},"http:\u002F\u002Fwww.quantcast.com\u002Fstackoverflow.com",{"_key":132,"_type":62,"children":133,"markDefs":147,"style":83},"adb70868d2e5",[134,138,143],{"_key":135,"_type":66,"marks":136,"text":137},"adb70868d2e50",[],"That said, I agree with ",{"_key":139,"_type":66,"marks":140,"text":142},"adb70868d2e51",[141],"35e1f4aad872","the overall conclusion that Todd Hoff reaches",{"_key":144,"_type":66,"marks":145,"text":146},"adb70868d2e52",[],":",[148],{"_key":141,"_type":80,"href":81,"reference":82},{"_key":150,"_type":62,"children":151,"markDefs":156,"style":157},"12f98abb1d1c",[152],{"_key":153,"_type":66,"marks":154,"text":155},"12f98abb1d1c0",[],"If you need to Google scale then you really have no choice but to go the NoSQL direction. But Stack Overflow is not Google and neither are most sites. When thinking about your design options keep Stack Overflow in mind. In this era of multi-core, large RAM machines and advances in parallel programming techniques, scale up is still a viable strategy and shouldn't be tossed aside just because it's not cool anymore. Maybe someday we'll have the best of both worlds, but for now there's a big painful choice to be made and that choice decides your fate.",[],"blockquote",{"_key":159,"_type":62,"children":160,"markDefs":170,"style":83},"b30367fb7fa5",[161,166],{"_key":162,"_type":66,"marks":163,"text":165},"b30367fb7fa50",[164],"159d9b52964d","Scaling up is definitely a viable solution",{"_key":167,"_type":66,"marks":168,"text":169},"b30367fb7fa51",[],", as both Plenty of Fish and we can attest.",[171],{"_key":164,"_type":80,"href":172,"reference":82},"http:\u002F\u002Fwww.codinghorror.com\u002Fblog\u002Farchives\u002F001279.html",{"_key":174,"_type":62,"children":175,"markDefs":197,"style":83},"f8e00715e5a9",[176,180,184,188,193],{"_key":177,"_type":66,"marks":178,"text":179},"f8e00715e5a90",[],"Like all of Todd's pieces, it is ",{"_key":181,"_type":66,"marks":182,"text":183},"f8e00715e5a91",[113],"exhaustively",{"_key":185,"_type":66,"marks":186,"text":187},"f8e00715e5a92",[]," researched and documented, and ",{"_key":189,"_type":66,"marks":190,"text":192},"f8e00715e5a93",[191],"b97af37d84b3","well worth your time to read",{"_key":194,"_type":66,"marks":195,"text":196},"f8e00715e5a94",[],". I was a little stunned how thorough it was, actually -- I doubt anyone outside our core development team has thought about our design and scaling this much!",[198],{"_key":191,"_type":80,"href":81,"reference":82},"2009\u002F07\u002F17","",{"code":202,"language":203},"\u003Cp>It was quite an honor to see that the \u003Ca href=\"http:\u002F\u002Fhighscalability.com\u002Fstack-overflow-architecture\">High Scalability Blog posted an entry on Stack Overflow\u003C\u002Fa>!\u003C\u002Fp>\n\u003Cp>We referred to the HSB, and its exhaustively detailed information about how other websites handle scaling, many times during the course of Stack Overflow development. And I've \u003Ca href=\"http:\u002F\u002Fwww.codinghorror.com\u002Fblog\u002Farchives\u002F001195.html\">cited it myself\u003C\u002Fa> when researching what we think is the largest public same-stack (Microsoft) website on the internet, Plenty of Fish. It's an excellent resource.\u003C\u002Fp>\n\u003Cp>I don't know if Stack Overflow has \u003Cem>that\u003C\u002Fem> much traffic relative to many of the other truly giant public websites profiled on the HSB. You can see \u003Ca href=\"http:\u002F\u002Fwww.quantcast.com\u002Fstackoverflow.com\">our public Stack Overflow traffic stats at Quantcast\u003C\u002Fa> if you're curious. Still, it's great to be able to give back to the community and help document our own process of scaling our little corner of the web.\u003C\u002Fp>\n\u003Cp>That said, I agree with \u003Ca href=\"http:\u002F\u002Fhighscalability.com\u002Fstack-overflow-architecture\">the overall conclusion that Todd Hoff reaches\u003C\u002Fa>:\u003C\u002Fp>\n\u003Cblockquote>\nIf you need to Google scale then you really have no choice but to go the NoSQL direction. But Stack Overflow is not Google and neither are most sites. When thinking about your design options keep Stack Overflow in mind. In this era of multi-core, large RAM machines and advances in parallel programming techniques, scale up is still a viable strategy and shouldn't be tossed aside just because it's not cool anymore. Maybe someday we'll have the best of both worlds, but for now there's a big painful choice to be made and that choice decides your fate.\n\u003C\u002Fblockquote>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fwww.codinghorror.com\u002Fblog\u002Farchives\u002F001279.html\">Scaling up is definitely a viable solution\u003C\u002Fa>, as both Plenty of Fish and we can attest.\u003C\u002Fp>\n\u003Cp>Like all of Todd's pieces, it is \u003Cem>exhaustively\u003C\u002Fem> researched and documented, and \u003Ca href=\"http:\u002F\u002Fhighscalability.com\u002Fstack-overflow-architecture\">well worth your time to read\u003C\u002Fa>. I was a little stunned how thorough it was, actually -- I doubt anyone outside our core development team has thought about our design and scaling this much!\u003C\u002Fp>","html","2009-07-17T12:00:00.000Z",{"current":206},"high-scalability-blog-on-stack-overflow",[208,216,221],{"_createdAt":209,"_id":210,"_rev":211,"_type":212,"_updatedAt":209,"slug":213,"title":215},"2023-05-23T16:43:21Z","wp-tagcat-background","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":214},"background","Background",{"_createdAt":209,"_id":217,"_rev":211,"_type":212,"_updatedAt":209,"slug":218,"title":220},"wp-tagcat-company",{"current":219},"company","Company",{"_createdAt":209,"_id":222,"_rev":211,"_type":212,"_updatedAt":209,"slug":223,"title":225},"wp-tagcat-server",{"current":224},"server","Server","High Scalability Blog on Stack Overflow",[228,234,240,246],{"_id":229,"publishedAt":230,"slug":231,"sponsored":82,"title":233},"76c9771b-34e6-4d98-8641-ecefc711f0ef","2026-07-06T15:23:34.559Z",{"_type":10,"current":232},"when-the-sensor-starts-thinking-snortml-agentic-ai-and-the-evolving-architecture-of-intrusion-detection","When the sensor starts thinking: SnortML, agentic AI, and the evolving architecture of intrusion detection",{"_id":235,"publishedAt":236,"slug":237,"sponsored":82,"title":239},"28e560af-f0aa-4d46-bd90-f435ad604aa7","2026-06-26T14:00:27.102Z",{"_type":10,"current":238},"paging-charity-how-can-engineering-leaders-avoid-becoming-bond-villains","Paging Charity! How can engineering leaders avoid becoming Bond villains?",{"_id":241,"publishedAt":242,"slug":243,"sponsored":82,"title":245},"4b22c2a3-3779-4966-93eb-5230391dbdce","2026-06-23T14:08:58.595Z",{"_type":10,"current":244},"your-ai-shipped-a-backend-that-boots-that-is-the-whole-problem","Your AI shipped a backend that boots. That is the whole problem.",{"_id":247,"publishedAt":248,"slug":249,"sponsored":82,"title":251},"5cf362e1-fe7b-45af-b69c-914731c6a052","2026-06-23T14:00:00.000Z",{"_type":10,"current":250},"the-2026-developer-survey-is-now-open-for-human-developers-only","The 2026 Developer Survey is now open (for human developers only)!",{"data":253,"sourceMap":-1},{"count":254,"lastTimestamp":82},0]