N2O - The Most Powerful Web Framework
summary
N2O is a fork of Nitrogen that trades Nitrogen’s heavy process registry for removed process registry and runs entirely in Cowboy worker contexts, switches to ETS and binaries for page construction, and uses gproc for session linking; it focuses on WebSockets (with XHR fallback) and a uniform DB layer for Riak/Mnesia/KV. A homegrown Erlang-to-JS compiler outputs readable React-compatible JS, and benchmarks claim up to 13,000 TCP connections (7x faster than Nitrogen; raw nginx hits ~60k). An open‑source CMS and examples exist on GitHub.
AI-written summary · about
chapters (24)
- 0:00Introduction to N2O
- 1:03Web framework classification
- 2:38Functional DSL frameworks
- 5:55The Clojure stack influence
- 6:27Challenges in N2O design
- 8:14Web server benchmarks
- 9:45Existing Erlang frameworks
- 10:32Evolution of N2O
- 11:11Architectural improvements
- 14:28System layer design
- 16:19Benchmark analysis
- 19:03Deferring JS rendering
- 20:38Externalizing HTML rendering
- 21:44Real single page apps
- 21:55Conceptual architecture
- 22:09Specifying UI elements
- 22:41DSL implementation details
- 23:04Desktop-like development
- 23:28Compiler theory and goals
- 26:42Applying the JS compiler
- 33:17Elixir and N2O
- 34:25Data handling and REST
- 38:49Community and resources
- 41:01Q&A and closing
related talks
37mFireside chat on Nova and Nitrogen
36mVision for Nitro 2024
10mUnifying Web Development: Nitro and UnJS
24mNitro, the Server toolkit you probably need
40mZotonic: Erlang for the Web
23mWeb Development Without Drugs Using PostgreSQL, Nginx and c2h5oh
38mBuilding a Framework for the Edge
25mNext-Gen Server JavaScript: Web Standards