Zero downtime Deployment on Kubernetes
summary
Shows a zero-downtime path that keeps a service live while changing a database schema: Kubernetes rolling upgrades plus a streaming pipeline that does initial bulk copy and then continuous replication of writes so new pods see up-to-date rows. Uses Hazelcast for the streaming job and session replication and a CDC connector (Debezium-style) to capture DB changes, with a Spring Boot app on the pods and a MySQL→Postgres-capable pipeline. Demo runs the forward job, migrates live writes, and the service stays up.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:25Why zero downtime matters
- 3:54Blue green vs rolling upgrades
- 7:04Breaking schema changes
- 9:08Breaking changes in e-commerce
- 11:17Multi-step migration strategy
- 14:32Data streaming and CDC
- 17:01Kubernetes streaming setup
- 21:18Hazelcast and Debezium demo
- 22:43Live demo walkthrough
- 30:13Key takeaways and Q&A
related talks
35mZero-Downtime Deployment on Kubernetes
35mZero-downtime deployment on Kubernetes
31mZero downtime deployment with Kubernetes, Spring Boot and Flyway
43mZero-downtime deployment with Kubernetes, Spring Boot and Flyway
50mZero Downtime Migrations with Spring Boot
25mAutomating Kubernetes Upgrades for Zero Downtime
38mZero-downtime deployment with Kubernetes, Spring Boot and Flyway
40mStrategies for Zero Down Time, Frequent Deployments
