Panel on Microservices
summary
Panelists argue cloud-native beats naive multi-cloud for operational simplicity and cost, citing migrations that cut compute bills 70–90% cost reduction after rearchitecting to cloud services; they recommend tackling data first with patterns like a virtual database layer to avoid costly removes. API design uses centralized reviewers—API bar raiser—and treats public APIs as effectively permanent. Security and GDPR drive continuous updates and training. Kubernetes is described as a useful but low-level building block to standardize deployments.
AI-written summary · about
chapters (9)
- 0:00Microservices panel intro
- 1:37Multi-cloud vs single-cloud
- 6:05Monolith to microservices
- 9:13Human factor in adoption
- 15:56Cost of microservices
- 18:56Security in microservices
- 20:47Interfaces and boundaries
- 25:45Team coordination
- 29:41Project vs product mindset
related talks
40mPanel Discussion: Going Multi-Cloud for Realz. Stories From Media, Retail, & Infrastructure
42mPanel: Architecture
08mThe Evolution of Microservices Architecture in Cloud-Native
47mMicroservice Panel
50mJourneys To Cloud Native Architecture: Sun, Sea & Emergencies
28mCloud Chaos and Microservices Mayhem
20mMicroservices in the future
34mCloud Chaos and Microservices Mayhem
