Downloaded 11 times
Uploaded byMickaël Rémond
Building Scalable Systems: What you can learn from Erlang - DotScale 2016
The document outlines the evolution of scalable systems, starting with the actor model proposed by Carl Hewitt in 1973, leading to the development of Erlang in 1986, which emphasizes handling failures and lightweight processes. It highlights the strengths of Erlang's VM in both vertical and horizontal scaling, particularly for server applications that are often IO and memory bound. Finally, it notes that Erlang continues to be a reference for scalable systems, influencing newer languages and frameworks like Elixir and Go.
More Related Content
Similar to Building Scalable Systems: What you can learn from Erlang - DotScale 2016
Building Scalable Systems: What you can learn from Erlang - DotScale 2016
- 1. Building Scalable Systems Whatyou can Learn from Erlang
- 3.
- 4. Actor Model • CarlHewitt
- 5. Actor Model Principle •An actor can: • Send Messages to other Actors • Create other Actors • Process Next Message
- 6.
- 7. “An Island ofSanity in a Sea of Concurrency" Actor State Actor State Actor State Actor State Actor State
- 8.
- 9.
- 10. Birth of Erlang JoeArmstrong, Robert Virding, Mike Williams, Bjarne Däcker
- 11. Share Nothing withLightweight Processes
- 12.
- 13. Handle Failures withProcess Links and Supervisors
- 15.
- 16. Erlang VM releasedas Open Source
- 17. Erlang strength liesin the VM
- 18. Vertical scaling: Multicore andScheduler
- 19.
- 20. Erlang strengths match Serverapplications properties • Server apps are most of the time IO bound • Server apps are often memory bound.
- 21. Network Stack Accepted connections Requests processing Serverthreads Pool Thread Thread Thread Thread Thread Thread Thread Thread Thread … Client Requests X X X Connections Pool i.e. Apache
- 22. Network Stack Accepted connections Requests processing Lightweightprocesses Client Requests … One Connection per Thread Erlang webservers i.e. Yaws, Cowboy, etc.
- 23. Design comparison • Numberof requests handled in peak time: 1Ks to 10ks • Throughput: reduce quickly when max concurrency reached • More complex code • Number of concurrent requests handle in peak time: 100Ks to 1Ms • Throughput: Higher for large number of concurrent requests. • Simple code, no pool to manage Design with worker thread pools Design with Erlang processes
- 24.
- 25. Erlang is stillthe Reference for Scalable Systems
- 26. Makes it easierto build Advanced Concurrency Patterns
- 27. New languages usingthe Erlang VM: Elixir, LFE, etc
- 28. Inspiration for newlanguages / Frameworks: Go, Scala, Akka, Clojure, …
- 29.