Cloud Native Landscape for Node.js Developers
summary
Overview of practical steps to go cloud native for Node.js: packaging with Dockerfiles, deploying images to registries and Kubernetes using YAML deployments and Services, and implementing liveness and readiness probes (HTTP/TCP/exec) to enable self‑healing. Emphasis on exporting metrics (Google’s four golden signals) and using Prometheus metrics plus logging to stdout for aggregation. Mentions CNCF landscape size (over 1500 projects) and tools like IBM Code Engine, Skaffold and Stern for local dev and CI/CD.
AI-written summary · about
chapters (23)
- 0:00Start
- 2:49Microservices
- 3:26Why Do We Want To Use Microservices Architecture in the Cloud Native World
- 4:39The Downsides of the Market Microservices Architecture
- 5:29The 12-Factor Application
- 6:06Code Base
- 6:19Dependencies
- 7:41Dev Prod Parity
- 8:39How Do You Convert Your Existing Applications To Be More Cloud Native
- 10:07Package Json
- 10:22Docker File
- 12:09Kubernetes
- 13:07Deployment
- 15:01Load Balancer
- 15:18Cluster Ip
- 16:01Health Checks
- 17:21Http Probe
- 19:37Monitoring
- 19:53Google's Four Golden Signals
- 20:43Prometheus
- 21:20Logging
- 22:58Ipm and Red Hat Node Js Reference Architecture
- 24:28Ibm Code Engine
related talks
23mMaking Cloud Native Computing Universal and Sustainable
20mCloud Native: The Building Blocks for the Human Experience
46mCloud Native Approach for Node.js Developers
50mFlying through Cloud Native (CNCF)
18mCloud Native for Humans
56m## Developer toolchain the cloud native way
30mNode.js in a Kubernetes World
50mJourneys To Cloud Native Architecture: Sun, Sea & Emergencies