Thinking in a Highly Concurrent, Mostly-functional Language
summary
Concrete claims and concrete artifacts: an ATM switch prototype reaches 30,000 calls per pair of boards by moving from monolithic processes to a process per concurrent activity design and using an ETS table for state, an XMPP proxy refactor jumps from handling four messages to ~512 concurrent sockets, MongooseIM hits one million simultaneous connections on BEAM, and removing a serial gen_server bottleneck multiplies web throughput — shows what was built, why it changed, and which bottlenecks mattered.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 6:53Syntax
- 7:14Concurrency
- 12:05Ericsson
- 13:38Ericsson XT301
- 19:18Active Standby
- 20:28Messaging Proxy
- 24:25Refactoring
- 27:00Mongoose
- 27:50EJ Body
- 31:00Instant Messaging Architecture
- 37:46Stress Testing
- 40:19Joe Armstrong
- 41:09Multicore
- 42:39Ruby on Rails
- 43:04ChicagoBoss
- 43:39The Law
- 44:23Multicore architectures
- 45:06React
- 46:13Erlang Zen
- 48:05Steven Offski
