<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Stretched Clusters on This Is My Demo</title><link>https://thisismydemo.cloud/tags/stretched-clusters/</link><description>Recent content in Stretched Clusters on This Is My Demo</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 05 Apr 2026 17:46:25 +0000</lastBuildDate><atom:link href="https://thisismydemo.cloud/tags/stretched-clusters/index.xml" rel="self" type="application/rss+xml"/><item><title>WSFC at Scale</title><link>https://thisismydemo.cloud/post/wsfc-at-scale/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>https://thisismydemo.cloud/post/wsfc-at-scale/</guid><description>&lt;p&gt;A two-node cluster is an architecture decision. A 64-node cluster is a lifestyle choice.&lt;/p&gt;
&lt;p&gt;Posts 5 through 8 built your first cluster. Posts 9 through 15 hardened, monitored, secured, and protected it. This post asks the question that comes next: what happens when you need more?&lt;/p&gt;
&lt;p&gt;Scaling Hyper-V is also where the economics need to stay honest. The goal is not to recreate every premium reference architecture just because it exists. The goal is to scale a platform that is already cheaper than the VCF path and often more flexible than an Azure Local design that assumes new hardware and a new recurring bill.&lt;/p&gt;</description></item></channel></rss>