Object Oriented Thinking with Elixir and OTP
summary
Claims that Erlang/Elixir processes behave like objects and shows it by building a contrived chat history service, implementing it first as a tail-recursive loop and then as a GenServer start_link with a client API. Demonstrates message passing, call vs cast for sync vs async, and how tail recursion avoids stack overflow. Explains linking, supervision trees and restart strategies, points out SMP and distributed Erlang for scaling, and shows the GenServer version turns asynchronous mailboxes into synchronous, maintainable calls.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:52Erlang
- 4:33Object Oriented Thinking
- 4:45Actor Model
- 5:18Distributed Airline
- 6:23Preserve Your State
- 10:20Client Api
related talks
50mA Peek Inside Erlang's OTP
40mJumping gen_servers! A new way of building (...) applications
39mConcurrency Oriented Programming In A Modern World
38mOTP, the Middleware for Concurrent Distributed Scalable Architectures
41mIdioms for building fault-tolerant applications with Elixir
01h 01mThe Erlang Ecosystem
51mThe Erlang VM or How I Started Loving Parallel Progamming
52mConcurrency Oriented Programming in a Modern World