The BEAM in the Cloud Native era
summary
Claim: the BEAM (Erlang/Elixir) already implements fault tolerance, supervision trees, and lightweight distribution that many cloud‑native projects reinvent, so relying on Kubernetes and dozens of add‑ons for app resilience adds unnecessary complexity. Concrete notes: use BEAM (Erlang/Elixir) fault-tolerance at the application level and reserve Kubernetes for orchestration only (packaging and delivery), expect roughly four major Kubernetes release cycles a year, and monitor with Prometheus is solid. Contribution path: fix orchestration bugs or map failure modes (database connections) between layers.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:19What I Do for a Living
- 1:11Introduction
- 4:13Definitions
- 7:22Cloud Native Development
- 7:49Continuous Delivery
- 8:37Micro Services and Containers
- 13:13Container Registries
- 27:51Cons
related talks
10mBack to the Future
47mBEAM Architecture Handbook
34mDistributed applications and Kubernetes
51mThe Erlang VM or How I Started Loving Parallel Progamming
36mResilient Multi-Cloud Strategies: Harnessing Kubernetes, Cluster API, and Cell-Based Architecture
53mIdioms for Building Distributed Fault-tolerant Applications with Elixir
42mThe Soul of Erlang and Elixir
09mThe cloud native elephant in the room