Panel Discussion: The number of orche
summary
Panel debates concrete tradeoffs: Kubernetes, AWS autoscaling groups, Spinnaker, DC/OS/Mesos, CRI‑O/Podman and cert-manager all appear with real pros and cons. Teams learn by solving a deployment problem, start with familiar stacks, and keep an exit plan to avoid migration pain; cost and operator effort often trump hype. Simplicity and observability (Prometheus/Datadog/Honeycomb) drive developer efficiency, cron‑based rollouts still persist, and choosing hosted services versus DIY depends on scale, budget and who’s available to run it.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 2:01Panel Introductions
- 14:33Audience Participation
- 15:56Start with the problem
- 17:32Accept the learning curve
- 18:59Finding the right person
- 19:37Growing confidence
- 20:05Technology investments
- 21:57Have a pass out
- 23:02No lockin
- 23:47Sun cost
- 24:47Software proliferation
- 25:04Big complex problems
- 25:41Industry decisions
- 26:07Netflix
- 27:20Chicken and Egg
- 28:39Developer Efficiency
- 28:55Kubernetes
- 29:40Complexity
- 29:53Complexity is easy
- 31:09The observability aspect
- 32:25Team scale
- 33:13What makes our systems better
- 33:56How can we make it better
- 35:59Life cycle of technology
- 37:39Cost optimized
- 39:35Simplicity
- 42:52Law of stretched systems
- 43:18How teams deal with stretched systems
- 43:36Coping with complexity
- 43:50Punishment
- 45:18I was old
related talks
31mPanel Discussion: Platform and Developer Productivity - Trends and Challenges
42mMastering Kubernetes: Challenges, Strategies, and Best Practices
46mDeploying and maintaining software for today's infrastructure
52mPanel Discussion
39mKeynote Panel: Straight Talk from Technology Leaders on Spinnaker & the SDLC
36mPanel Discussion: Leveraging Cloud Native Technology to Transform Your Enterprise
44mIndustry Executive Panel featuring
33mPanel Discussion: Spinnaker Success - CD as a Service using Spinnaker