Elixir 101 - The Erlang VM

A brief introduction of the BEAM (The Erlang VM), that paves the way to talk about Elixir.

Transcript

1. elixir 101 part 1/2
2. @juanzuluaga
3. BEAM The Erlang VM
4. disclaimer
5. I'm just a curious noob
6. history
7. • created at Ericsson in 1986
8. • created at Ericsson in 1986 • open sourced in 1995
9. • created at Ericsson in 1986 • open sourced in 1995 • current version 18.1
10. created to solve telephony applications
11. the original Ericsson switches had ~5MB of memory
12. it powers ~40% of all the mobile traffic (LTE, SMS, 3G) across Europe
13. features
14. • high availability
15. the legendary nine nines
16. the legendary 99,9999999%
17. that's ~31ms/year
18. • high availability • fault tolerant (self healing)
19. supervised applications (modules)
20. • high availability • fault tolerant (self healing) • distributed
21. • high availability • fault tolerant (self healing) • distributed • concurrent
22. solved the c10k problem
23. and the c100k problem
24. 30 years ago!
25. • high availability • fault tolerant (self healing) • distributed • concurrent • hot code loading (zero downtime deploys)
26. • high availability • fault tolerant (self healing) • distributed • concurrent • hot code loading (zero downtime deploys) • great tooling (demo)
27. internals
28. processes
29. these are not OS processes
30. very lightweight abstraction running on the BEAM
32. • cheap to create and destroy
33. • cheap to create and destroy • completely isolated
34. • cheap to create and destroy • completely isolated • memory is not shared
35. • cheap to create and destroy • completely isolated • memory is not shared • communication over messages
36. • cheap to create and destroy • completely isolated • memory is not shared • communication over messages • supervised (different strategies)
37. • cheap to create and destroy • completely isolated • memory is not shared • communication over messages • supervised (different strategies) • distributed
38. sounds familiar?
39. sounds familiar? the actor model
40. garbage collector
41. • generational (old & new zones)
42. • generational (old & new zones) • collected per process
43. • generational (old & new zones) • collected per process • no need if the process finished
44. • generational (old & new zones) • collected per process • no need if the process finished • no global pauses
45. scheduler
46. • the BEAM creates 1 per core
47. • the BEAM creates 1 per core • memory is not shared
48. • the BEAM creates 1 per core • memory is not shared • perform load balancing
49. • the BEAM creates 1 per core • memory is not shared • perform load balancing • guarantees that a process won't block others
50. BEAM
51. companies using the BEAM
52. • Whatsapp (2 million users/server)
53. • Whatsapp (2 million users/server) • Facebook
54. • Whatsapp (2 million users/server) • Facebook • Goldman Sachs (High frequency trading)
55. • Whatsapp (2 million users/server) • Facebook • Goldman Sachs (High frequency trading) • github (git proxy, gh-pages, gists)
56. • Whatsapp (2 million users/server) • Facebook • Goldman Sachs (High frequency trading) • github (git proxy, gh-pages, gists) • heroku
57. • Amazon SimpleDB
58. • Amazon SimpleDB • RabbitMQ
59. • Amazon SimpleDB • RabbitMQ • CouchDB
60. • Amazon SimpleDB • RabbitMQ • CouchDB • Riak
61. really? using a 30 y/o tech?
62. it's under very active development
63. erlang 18 was released 30 days ago
64. why is the industry looking back?
65. telcos had tough constrains
66. we're experiencing problems that were solved 30 years ago
67. problems that were hidden by the Moore's Law
68. erlang in 1 minute
69. purely functional lang
70. data is immutable
71. powerful pattern matching
72. actor based concurrency
74. OTP Open Telecom Platform
75. huge repository of all kinds of libraries
76. • crypto
77. • crypto • http servers
78. • crypto • http servers • tcp servers
79. • crypto • http servers • tcp servers • realtime distributed databases
80. • crypto • http servers • tcp servers • realtime distributed databases • GUI and graphics
81. thanks!
82. questions?