Building Your First Stateful DC/OS Service
summary
DC/OS SDK produces a runnable scheduler package: author builds a stub universe jar, uploads artifacts to S3, and installs via Cosmos; the demo launches a memcached framework with three pods (each reserving CPU and RAM, e.g. 0.1 CPU/256MB or 1 CPU/1GB), shows offer evaluation and reserved ports, uses an executor-level volume to share a dynamic port, adds a sidecar plan that flushes caches, exercises task exec to inspect sandboxes, and demonstrates install, restart/replace semantics and a full uninstall that unreserves volumes.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:58Agenda
- 3:54Who am I?
- 5:00Why the SDK?
- 7:30What is the SDK?
- 8:15What's built-in?
- 11:04Three core interfaces
- 11:28Declarative API
- 16:24Programmatic API
- 18:01REST API
- 22:29Docker!
- 24:25Enter Docker container
- 39:42Hello, world!
- 40:23A note on the dev cycle.
- 41:15Memcache
- 47:20Adding a template
related talks
32mDataStax Enterprise on DC/OS - Yes, It’s Possible; Customer Case Studies
48mContainer: check! Aber wohin mit Persistent Data, Big Data oder Fast Data?!
01h 19mTutorial: Back to Basics: Hands-On Deployment of Stateful Workloads on Kubernetes
51mExploring Stateful Microservices in the Cloud Native World
42mDistributed Data Stores on Kubernetes
41mUsing External Persistent Volumes to Reduce Recovery Times and Achieve High Availability on DC/OS
39mContainerize Microservices with Service Fabric
37mNext-Level Powers: Enhance Your IDP with the WASM and Dapr Hero Team-Up!
