Rewind 07 – Modern Software Protects Itself – Older Software Doesn't

Modern software protects itself; older software relies on the infrastructure to protect it. In this short episode, Jens explains why that one difference decides what your hardware has to look like, and why it gets skipped in almost every modernization discussion. He describes a node design that serves both worlds on the same hardware foundation. In this episode Two kinds of software with opposite demands: cloud-native applications versus classic single-instance software One hardware foundation, two protection models: NVMe-dense nodes as vSAN ESA hosts or as Kubernetes workers with Portworx Bringing local NVMe, a FlashBlade object tier and existing Dell EMC systems behind one consistent data layer Protection on demand instead of the watering can, and reacting to storage supply shortages without rethinking the stack Why you don't have to choose between old and new while running VMware for a while longer Originally published in German on June 16, 2026: https://klasen.ai/briefing/software-schuetzt-sich-selbst/ English version: https://klasen.ai/en/briefing/software-schuetzt-sich-selbst/ Voices are AI-generated (Jens's voice is a clone of his own). Content and analysis by Jens Klasen. Disclosure: This briefing mentions Portworx. Jens has worked for Everpure (formerly Pure Storage) and the Portworx team since September 16, 2026 – this briefing was written before he joined.