>What if we built a new IT stack that was designed to be obliterated and reconstructed every 24 hours with latest patch builds each time? Inevitably an update

>What if we built a new IT stack that was designed to be obliterated and reconstructed every 24 hours with latest patch builds each time? Inevitably an update is going to break something. So even if you can automate all of that, how can you make sure it doesn't break something? This requirement isn't just the automation and technology gathering, it's testing too. It seems to me like you'd need a lot more benefits to make this worth the time/money/effort. You'd probably be better off having 2 networks for employees: 1 for public internet and 1 for internal company stuff. I think the intelligence community has something like that?