Message passing for actors and humans with Raxx
summary
Raxx treats HTTP as messages and implements per-connection Elixir processes (Ace) so each request becomes an actor with a mailbox; streaming maps to head/body/tail callbacks and responses stream as message chunks. A browser-side prototype, GenBrowser, gives each client an address and an unforgeable signed cursor so servers can send direct messages to mailboxes. The system runs in production for two years, supports millions of lightweight processes (tens of thousands tested in JS), and uses signed addresses to prevent forgery. Raxx treats HTTP as messages GenBrowser gives each client an address
AI-written summary · about
chapters (6)
- 0:00Understanding the actor model
- 3:01Building an actor system
- 12:29Benefits of the actor model
- 18:31Implementing a web server
- 25:38Client-server communication
- 35:16Q&A and closing thoughts
related talks
06mIntroducing Raxx, an Elixir Webserver Interface
34mPurify your web development with Raxx
53mRSocket - future Reactive Application Protocol?
40mReactive message driven service 2 service communication with RSocket
29mRealtime web applications with streaming REST
28mIntroducing RIG – the Reactive Interaction Gateway
44mElixir & Phoenix - Fast, Concurrent and Explicit
53mMultiplayer Pac-Man with RSocket