Hold My State: The Problems of Process State
summary
Live demos show a human substitute acting as a process to prove that cast vs call demo yields different failure modes: casting floods the message queue and leads to a crash when state is requested, while calling enforces backpressure but turns the process into a bottleneck. A ten‑second request timeout is used in the demo (10-second timeout). Advice includes watching reductions, queue length and memory with Observer tool and references Programming Erlang and Designing for Scalability with Erlang/OTP.
AI-written summary · about
chapters (7)
- 0:00Process state in Elixir
- 1:53Erlang vs OOP message passing
- 3:48Casting with single process
- 7:10Calling with single process
- 10:37Scaling with workers
- 14:56Warning signs in production
- 16:40Q&A
related talks
40mComparison and Commentary on "Application Operating System"
32mModern Erlang Teaching from Code Refactoring to Actor System Verification
01h 35mThinking Outside the Synchronisation Quadrant
39mConcurrent Languages are Functional
51mThe Erlang VM or How I Started Loving Parallel Progamming
43mConcurrency Oriented Programming in a Modern World
43mConcurrency Abstractions for Application Security
23mElixir GenServer: Understanding Elixir concurrency model