Challenges to Writing Cloud Native Applications
summary
Defines cloud native as containerized, dynamically orchestrated, service-oriented and contrasts Kubernetes/Docker platforms with legacy VMs; catalogs four persistent-storage patterns including unreplicated shards and tradeoffs between Postgres vs Cassandra for multi-master needs; recommends CDN storage (S3/GCS) and pod colocation for low-latency calls; shows a demo tool that queries Postgres with batch SQL with 40 IDs to cut many round trips into a single query (0.01–0.015 ms).
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:50What Makes Software Cloud Native?
- 3:41What is a Cloud Platform?
- 4:21Roles: The Runtime Environment
- 5:31Roles: Network Provider
- 7:34Persistent Data Storage: Single Replica
- 8:27Persistent Data Storage: Unreplicated Shords
- 8:56Persistent Data Storage Multiple volatile coples
- 9:19Persistent Data Storage: Runtime data replication
- 12:23Service Coupling: What To Couple
- 13:37Service Coupling: When Not To
- 15:53Internal API Calls: Simplifying API Actions
- 16:34Internal API Calls: Batch Endpoints
- 17:25Internal API Calls: Caching
- 17:57Testing
- 20:37Local Development
- 26:12Some Suggested Reading
related talks
53mStreamline Cloud-Native App Development Using CDEs
39mCI/CD, APIs, and Scaling: What Every Cloud Native Developer Needs To Kn...
24mA Cloud Native Foundation For Developer/Application Platforms
27mHow Containers Complicate Successful Cloud Native Transformation
46mIn Search of the Perfect Cloud Native Developer Experience
52mCloud Native Developer Experience in 2025
51mYour Cloud-Native Toolbox for Java
50mCloud-Native Dev Tools: Bringing the cloud back to earth