Send us a text In this episode of DevOps Sauna, Pinja and Stefan unpack what a good incident response actually looks like, from the moment an issue is discovered to recovery, communication, and learning afterward. They dive into real-world incident management practices: defining incident severity, assigning the right roles, running mock incidents, validating backups, and communicating clearly without panic. The conversation also tackles one of the hardest topics in engineering culture: blamel...
All content for DevOps Sauna from Eficode is the property of Eficode and is served directly from their servers
with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.
Send us a text In this episode of DevOps Sauna, Pinja and Stefan unpack what a good incident response actually looks like, from the moment an issue is discovered to recovery, communication, and learning afterward. They dive into real-world incident management practices: defining incident severity, assigning the right roles, running mock incidents, validating backups, and communicating clearly without panic. The conversation also tackles one of the hardest topics in engineering culture: blamel...
Who controls your cloud now? Inside Europe’s shift to sovereign cloud
DevOps Sauna from Eficode
25 minutes
3 weeks ago
Who controls your cloud now? Inside Europe’s shift to sovereign cloud
Send us a text Who really controls your cloud, and why does it matter now? In this episode of DevOps Sauna, Pinja and Stefan dive into Europe’s growing shift toward sovereign cloud. They explore what’s driving the conversation, from data sovereignty and GDPR to geopolitical uncertainty and upcoming EU regulations. The discussion breaks down how different countries approach sovereign cloud, what this means for cloud providers and enterprises, and how DevOps teams are affected in practice. From...
DevOps Sauna from Eficode
Send us a text In this episode of DevOps Sauna, Pinja and Stefan unpack what a good incident response actually looks like, from the moment an issue is discovered to recovery, communication, and learning afterward. They dive into real-world incident management practices: defining incident severity, assigning the right roles, running mock incidents, validating backups, and communicating clearly without panic. The conversation also tackles one of the hardest topics in engineering culture: blamel...
