Modern Abstractions and the Web, and avoiding Pitfalls because Life is short
summary
Compares concrete tradeoffs: Erlang style process isolation gives each request its own heap so a misbehaving task can be killed and restarted, Elixir + Phoenix run on that VM to deliver cheap concurrency and real fault tolerance, preemptive scheduling prevents a single infinite loop from consuming all cores, practical pitfalls include the binary heap and permanent atom table garbage issues, and a Kudos prototype built with Phoenix proves the stack is fast, scalable, and pleasant to develop with.
AI-written summary · about
chapters (8)
- 0:00Start
- 16:51Java Virtual Machine
- 18:50Concurrency Abstractions
- 19:01Concurrency Models
- 25:32Binary Space
- 28:32Object Oriented Pattern Principles
- 31:33Web Framework
- 32:56Php
related talks
44mElixir & Phoenix - Fast, Concurrent and Explicit
41mIdioms for building fault-tolerant applications with Elixir
41mElixir & Phoenix – fast, concurrent and explicit
32mWhy I choose Phoenix
48mElixir by the Bellyful
44mIdioms for Building Fault-tolerant Applications with Elixir
42mIt's about (run)time -- Elixir beyond the hype
03h 19mWorkshop - All Aboard The Elixir Express!