A Peek Inside Erlang's OTP
summary
Erlang OTP is shown as a practical layer that turns ad-hoc message-loop code into managed services: the VM runs millions of lightweight processes quickly (examples of a million spawned in seconds and apps using ~200k), the scheduler preempts by reductions (on the order of thousands), and gen_server encapsulates the client/server pattern so state, calls, casts and timeouts are handled for you. The stack uses supervision trees and let it crash restart strategies to achieve live upgrades and resilient deployments.
AI-written summary · about
chapters (36)
- 0:00Introduction
- 0:23What is Erlang?
- 0:54Erlang's Origins
- 1:47Telecom Switch Requirements
- 3:20Multi-language VM
- 4:06Erlang Process Model
- 5:18Process Execution
- 5:42Process Preemption
- 6:36Erlang Process Architecture
- 8:37Let It Crash
- 12:12Assignment is pattern matching
- 15:23OTP Augments Erlang
- 15:58Design Principles behaviors: frameworks for common problems
- 18:00Other OTP Tools & Apps
- 19:14Standard Behaviors
- 19:53Purpose of Behaviors
- 22:25Key/Value Server Process
- 23:59Process State
- 24:27Receive-Evaluate Loop
- 26:03General Server Process
- 27:54Client Code for Stop
- 28:18Server Code for Stop
- 28:46Key/Value Server API
- 29:44Client: Store
- 30:36Server: Store
- 33:15Generic Parts
- 34:33Behavior Design
- 36:49Callbacks
- 39:25Starting a KV Server
- 40:54Implement store callback
- 41:12Implement find callback
- 44:28application Behavior
- 45:05Application Example
- 46:28Supervisor Features
- 47:46Process Problems Solved
- 48:10Benefits of Behaviors
related talks
01h 01mThe Erlang Ecosystem
38mOTP, the Middleware for Concurrent Distributed Scalable Architectures
12mObject Oriented Thinking with Elixir and OTP
48m"Handling Millions of Concurrent Users with Erlang OTP"
51mThe Erlang VM or How I Started Loving Parallel Progamming
39mConcurrency Oriented Programming In A Modern World
35mDiving into Erlang is a one-way ticket
04mFrancesco Cesarini interviewed at OSCON 2010