Purify your web development with Raxx
summary
Claims a purely functional web layer that avoids Plug's mutable connection pitfalls and shows concrete fixes: a custom ACE server that defaults to HTTP/2, a Raxx interface with handle_head/handle_data callbacks for streaming, and a working Water Cooler chat built on PG pubsub and Server-Sent Events using text/event-stream. Demonstrates solving raw-body re-read bugs, streaming without loading whole files, and supervising npm asset watchers with x-sync; the demo runs end to end though Raxx intentionally omits higher-level conveniences.
AI-written summary · about
chapters (42)
- 0:00Introduction
- 0:50Titles I turned down
- 1:09Plughole
- 1:22Crowd Hailer
- 1:33What is Raxx
- 3:22Start the service
- 3:47Rack Server
- 4:14Server Helper
- 4:47Supervision Trees
- 5:50Functional Programming Data
- 6:05Plug Con Object
- 6:42Pragmatic Language
- 7:13JSON Parser
- 8:32Streaming
- 10:17HTTP
- 11:10Elixir
- 11:39Simple Rack Server
- 12:07Rack Streaming
- 12:55HandleHead
- 14:49Memory Image
- 15:20MVC
- 15:43Rack Stack
- 15:59No Framework
- 17:01Calm Down Pebble
- 17:11Chat
- 17:28Start an application
- 17:44This is my application
- 18:09What it does
- 18:40Adding webelo
- 19:20Naming your web interface
- 20:23Adding a server
- 20:46Pattern matching
- 22:01Actions
- 23:05static
- 23:41post
- 24:16publish message
- 25:07subscribe to updates
- 28:02service and events
- 29:16why use frameworks
- 29:52brunch
- 30:09watchcss
- 31:28watchtask
related talks
06mIntroducing Raxx, an Elixir Webserver Interface
42mMessage passing for actors and humans with Raxx
29mRealtime web applications with streaming REST
58mUnderstand the Next Phase of Web Development
53mRSocket - future Reactive Application Protocol?
36mStreaming over the web with modern Ruby
22mServing content on the web: from PHP to RSC—and beyond
01h 21mReactive Web Applications