Containers & Orchestration: The Elixir way
summary
Claim: Kubernetes mostly solves deployment and delivery problems not the BEAM's in-process resilience so use each where it fits. Containerize property‑based test suites and run them in CI/CD to get fast, reproducible integration and test in production scenarios. Build or reuse Operators to automate Elixir release lifecycle, monitoring and scale tasks — there is an Operator Framework and operatorhub.io with Kafka Prometheus etc operators. For productivity choose a managed Kubernetes (DigitalOcean, AWS, OpenShift) rather than DIY clusters.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:30About me
- 1:11Latin American companies
- 1:29Technical people
- 1:45Advantages and disadvantages
- 2:20You have to justify everything
- 2:33You want to be resourceful
- 2:56More resources more resources
- 3:20Latin American Elixir community
- 4:32Veronicas background
- 5:03The balance
- 5:36The other way
- 6:23Red Hat
- 7:07Erlang or Elixir
- 7:39Why Elixir
- 8:22Why Go
- 9:17Go
- 11:32Context
- 12:25Why
- 14:33What is Kubernetes
- 18:37What Kubernetes sells
- 19:49The reality of Kubernetes
- 20:50Testing
- 25:14Operators
related talks
44mContain yourselves
16mLiving without pre-production environments
36mBring Back the Power of BEAM Deployments with DeployEx
20mKubernetes 101
37mShaping Applications for Docker, CoreOS, Kubernetes & Co.
42mIt (Only) Starts with Containers
14mUnleashing the Full Power of Container with Orchestration & Management Platform
33mCentralizing Kubernetes and Container Operations