Has Everyone Forgotten Application Workflows in Kubernetes?
summary
Argument: kubernetes handles resource scheduling but not business workflows, so a higher orchestration layer is needed. Concrete build: a customer-360 + sentiment pipeline that pulls from Twitter (only 10–15% of tweets have geolocation), publishes to Kafka → Snowflake pipeline, and runs analysis in containers managed by kubernetes Jobs, CronJobs and a DaemonSet agent with nodeSelector to limit placement. Demo creates and kills jobs, shows pods starting and cleanup, and runs on a Bitnami sandbox.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:15Application vs Resource Management
- 2:38Application vs Business
- 3:44What is Kubernetes
- 4:52Kubernetes Architecture
- 8:33Use Case
- 9:22Implementation
- 12:56Microservices
- 13:52Business Priorities
related talks
22mManaging Distributed Workflows at Scale
27mCrafting Resilient and Scalable Systems with Orchestration and Choreography Patterns on Kubernetes
36mAutomating Cloud-native Spark Jobs with Argo Workflows
36mSuccessful Kubernetes Development Workflows
42mDeveloper-first Workflows on Kubernetes
37mSpark and Flink Running Scalable in Kubernetes #bbuzz
32mKubernetes as a Platform Framework Journey from IaC Pipelines to K8s APIs
52mCloud-Native Kubernetes Workflows on AKS with Argo