Cloud Native: why, oh why?
summary
Cloud native means running on an orchestrator that can kill and restart instances so apps must accept ephemeral execution, enable scale to zero for functions, and achieve autoscaling and instant resource access. Expect teams to split a monolith into 50 microservices or more, use Kafka clusters for cross-cloud data sync, apply circuit breakers, service mesh and tracing for resilience and observability, and confront data isolation, deployment density and Java memory costs.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:34Cloud Native is
- 1:28Some (arbitrary) definition
- 3:45Enabler of Cloud Native
- 6:14From monolith to...
- 8:51Why go through this pain?
- 11:34Containers scale, not developers
- 14:30How to focus on how, not where
- 16:16Isolating apps
- 16:36Isolate your microservices
- 17:31Multi cloud
- 20:13Microservices Based Systems are a Mess
- 20:48Circuit Breakers to the Rescue
- 21:19To the rescue, unless...
- 22:53Message-Driven & Reactive Microservices
- 23:58Data at Rest = Data in Motion
- 24:45Reactive Systems - Harder, Better, Faster, Stronger
- 25:54Density challenge, a focus on Java
related talks
42mCloud Native Applications
55mWhat Does Cloud-native Mean Anyway?
14mCloud Native vs. Platform Native vs...
03mGoing (cloud) Native
43mCloud Native - effective computing at scale
09mThe cloud native elephant in the room
51mWhat Is This Cloud Native Thing Anyway?
31mCloud native: the cattle the pets and the germs