[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-category-infrastructure-and-operations":3,"blog-category-posts-infrastructure-and-operations":9,"blog-categories":53,"blog-tags":75},{"category":4,"error":8},{"name":5,"slug":6,"description":7,"seo":8},"Infrastructure and Operations","infrastructure-and-operations","DevOps, hosting, reliability and the operational work that keeps a system running once it is live.",null,{"posts":10,"pagination":49,"error":8},[11,33],{"id":12,"title":13,"slug":14,"excerpt":15,"cover":16,"coverAlt":20,"datePublished":21,"dateModified":21,"category":22,"author":23,"tags":26},"bvd2ofec0c5s9fio6y1owwai","Blue-Green, Canary, and Rolling Deployments, Compared Honestly","blue-green-canary-and-rolling-deployments-compared","Three deployment strategies, each with a real tradeoff attached. Here is what each one actually buys you and what it costs, without pretending one is universally best.",{"url":17,"width":18,"height":19,"alt":20},"https:\u002F\u002Fmedia.drieverse.com\u002Fdrieverse-media\u002Fcms\u002Fblue_green_canary_and_rolling_deployments_compared_cover_b298c385ee.png",1200,630,"Blue-Green, Canary, and Rolling Deployments, Compared Honestly - cover image (seed-blog-content-cover)","2026-09-05",{"name":5,"slug":6},{"name":24,"slug":25},"DrieVerse Tech","drieverse-tech",[27,29,31],{"name":28,"slug":28},"architecture",{"name":30,"slug":30},"observability",{"name":32,"slug":32},"decision-frameworks",{"id":34,"title":35,"slug":36,"excerpt":37,"cover":38,"coverAlt":40,"datePublished":21,"dateModified":21,"category":41,"author":42,"tags":43},"x241areyikdk5hz1bp7r0a10","What an Incident Runbook Should Actually Contain","what-an-incident-runbook-should-actually-contain","Most incident runbooks are either too vague to use under pressure or too detailed to keep current. Here is what actually earns a place in one.",{"url":39,"width":18,"height":19,"alt":40},"https:\u002F\u002Fmedia.drieverse.com\u002Fdrieverse-media\u002Fcms\u002Fwhat_an_incident_runbook_should_actually_contain_cover_0b0a204432.png","What an Incident Runbook Should Actually Contain - cover image (seed-blog-content-cover)",{"name":5,"slug":6},{"name":24,"slug":25},[44,45,47],{"name":30,"slug":30},{"name":46,"slug":46},"process-design",{"name":48,"slug":48},"risk-management",{"page":50,"pageSize":51,"pageCount":50,"total":52},1,12,2,[54,58,62,66,70,74],{"name":55,"slug":56,"description":57,"seo":8},"AI and Automation","ai-and-automation","Applied AI and automation: what it actually does inside a working system, and where a human stays in the loop.",{"name":59,"slug":60,"description":61,"seo":8},"Brand and Design","brand-and-design","Visual identity and interface design, and how a consistent design system holds together across a product.",{"name":63,"slug":64,"description":65,"seo":8},"Company","company","Updates from DrieVerse Tech: what we are building, shipping and learning.",{"name":67,"slug":68,"description":69,"seo":8},"Engineering","engineering","Software architecture, code quality and the engineering practice behind the systems we build.",{"name":71,"slug":72,"description":73,"seo":8},"Growth","growth","Search visibility, content and acquisition: the growth work that sits alongside a build rather than bolted onto it.",{"name":5,"slug":6,"description":7,"seo":8},[76,77,78,80,82,84,85,87,88,89],{"name":28,"slug":28},{"name":32,"slug":32},{"name":79,"slug":79},"discovery",{"name":81,"slug":81},"evidence-based-claims",{"name":83,"slug":83},"human-in-the-loop",{"name":30,"slug":30},{"name":86,"slug":86},"positioning",{"name":46,"slug":46},{"name":48,"slug":48},{"name":90,"slug":90},"technical-debt"]