Reactor vs. Proactor
summary
Clear difference: the reactor uses an event loop and OS calls like select/epoll to wait and dispatch handlers, so code must return quickly or a long blocking handler stalls everyone; both models often run single-threaded with optional helper threads. The proactor relies on true OS-level Asynchronous I/O (Linux AIO, Windows I/O completion ports), lets code issue async operations ahead of demand, and is more complex but avoids handler-induced stalls.
AI-written summary · about
related talks
40mReactive programming: lessons learned
34mReactive Architecture
59mSucceeding at Reactive Architecture
52mYou Keep Using That Word: Asynchronous And Interprocess Comms
47mObject Reactive Programming
25mReactor Under the Hood: Building a Graph-Based Saga Orchestrator in Elixir
38mThe Actor Model: a new mental model for React
15mReactifying your application