What Building Multiple Scalable DC/OS Deployments Taught Me About Running Stateful Services on DC/OS
recording made private on YouTubehttps://youtu.be/kxh2FJ6aTAM
summary
Multiple scalable DC/OS deployments expose concrete limits and fixes: local volumes being pinned to hosts and “one task per volume” force either Portworx-style cloud‑native storage or manual workarounds; dynamic provisioning, rolling upgrades, and replica placement across failure domains get solved with automation that rebuilds clusters from code and with testing in a production‑like environment. Failure injection with Torpedo and Chaos Monkey, monitoring via Prometheus and Grafana, automated snapshots to S3, and handling a 100 GB growth or losing one versus three nodes all prove out and reduce outage time.
AI-written summary · about
related talks
01h 35mBuilding Your First Stateful DC/OS Service
10m⚡ Lightning Talk: Navigating the Complexities of Stateful Workloads in Kubernetes
20mLightning Talk: Multi-Datacenter Strategies for Data Services
35mDataStax Enterprise on DC/OS - Yes, It’s Possible; Customer Case Studies
48mContainer: check! Aber wohin mit Persistent Data, Big Data oder Fast Data?!
34mData Management in Kubernetes – Backup, DR, HA
33mSponsored Session: Open Source Cloud Native Storage Solutions for Stateful Applications from ...
22mRunning distributed stateful system on Kubernetes - Beyond Statefulsets