So I used Erlang...is my system as scalable as they say it'd be?
summary
Shows how an Erlang echo service evolves into supervised clusters across nodes and how property based tests find real faults. Uses ProER property-based tests (QuickCheck style) to generate stateful operation sequences, runs 1,000,000 tests in under an hour on a modest laptop and 100,000 tests in ~2 hours for supervised scenarios. Implementation is tiny (tens to low hundreds of Erlang lines) while test specs stay compact (≈60–72 lines) and exercise failures like restarts and node-level kills.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 5:37Typical Systems
- 13:42Example
- 21:05Traditional testing
- 27:48Automated testing
- 29:22Supervised testing
- 31:07Supervisor with lots of children
- 33:41Are we happy
- 34:10How does it look in real life
- 34:46Ethic
- 35:43Backend
- 36:24Challenge
related talks
35mDiving into Erlang is a one-way ticket
01h 01mThe Erlang Ecosystem
36mStateful property-based testing: with a game logic case study
50mA Peek Inside Erlang's OTP
42mThe Soul of Erlang and Elixir
35mScaling Erlang cluster to 10,000 nodes
53mScaling robots and other stuff with Erlang
31mAn Open Erlang PaaS Done Right