Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Elixir 101 - The Erlang VM
Search
Juanda Zapata
October 21, 2015
Programming
5
330
Elixir 101 - The Erlang VM
A brief introduction of the BEAM (The Erlang VM), that paves the way to talk about Elixir.
Juanda Zapata
October 21, 2015
Tweet
Share
More Decks by Juanda Zapata
See All by Juanda Zapata
Principles of Visual Design
juanzuluaga
0
72
Adapter Pattern
juanzuluaga
0
170
Maintainable CSS
juanzuluaga
0
82
UI Fundamentals for Programmers
juanzuluaga
0
210
UI fundamentals for programmers
juanzuluaga
0
390
Programming in paradise
juanzuluaga
1
140
Intro to Ruby
juanzuluaga
1
700
Other Decks in Programming
See All in Programming
React Nativeならぬ"Vue Native"が実現するかも?_新世代マルチプラットフォーム開発フレームワークのLynxとLynxのVue.js対応を追ってみよう_Vue Lynx
yut0naga1_fa
2
1k
コードとあなたと私の距離 / The Distance Between Code, You, and I
hiro_y
0
190
Catch Up: Go Style Guide Update
andpad
0
250
スキーマ駆動で、Zod OpenAPI Honoによる、API開発するために、Hono Takibiというライブラリを作っている
nakita628
0
320
AI Agent 時代的開發者生存指南
eddie
4
2.1k
Goで実践するドメイン駆動開発 AIと歩み始めた新規プロダクト開発の現在地
imkaoru
4
900
フロントエンド開発のためのブラウザ組み込みAI入門
masashi
7
3.5k
オープンソースソフトウェアへの解像度🔬
utam0k
17
3.1k
他言語経験者が Golangci-lint を最初のコーディングメンターにした話 / How Golangci-lint Became My First Coding Mentor: A Story from a Polyglot Programmer
uma31
0
420
GC25 Recap: The Code You Reviewed is Not the Code You Built / #newt_gophercon_tour
mazrean
0
110
『毎日の移動』を支えるGoバックエンド内製開発
yutautsugi
2
290
社会人になっても趣味開発を続けたい! / traPavilion
mazrean
1
100
Featured
See All Featured
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
46
7.7k
GraphQLとの向き合い方2022年版
quramy
49
14k
Done Done
chrislema
185
16k
Principles of Awesome APIs and How to Build Them.
keavy
127
17k
Learning to Love Humans: Emotional Interface Design
aarron
274
41k
Optimizing for Happiness
mojombo
379
70k
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
21
1.2k
Building an army of robots
kneath
305
46k
BBQ
matthewcrist
89
9.9k
Typedesign – Prime Four
hannesfritz
42
2.8k
Docker and Python
trallard
46
3.6k
Leading Effective Engineering Teams in the AI Era
addyosmani
7
630
Transcript
elixir 101 part 1/2
@juanzuluaga
BEAM The Erlang VM
disclaimer
I'm just a curious noob
history
• created at Ericsson in 1986
• created at Ericsson in 1986 • open sourced in
1995
• created at Ericsson in 1986 • open sourced in
1995 • current version 18.1
created to solve telephony applications
the original Ericsson switches had ~5MB of memory
it powers ~40% of all the mobile traffic (LTE, SMS,
3G) across Europe
features
• high availability
the legendary nine nines
the legendary 99,9999999%
that's ~31ms/year
• high availability • fault tolerant (self healing)
supervised applications (modules)
• high availability • fault tolerant (self healing) • distributed
• high availability • fault tolerant (self healing) • distributed
• concurrent
solved the c10k problem
and the c100k problem
30 years ago!
• high availability • fault tolerant (self healing) • distributed
• concurrent • hot code loading (zero downtime deploys)
• high availability • fault tolerant (self healing) • distributed
• concurrent • hot code loading (zero downtime deploys) • great tooling (demo)
internals
processes
these are not OS processes
very lightweight abstraction running on the BEAM
None
• cheap to create and destroy
• cheap to create and destroy • completely isolated
• cheap to create and destroy • completely isolated •
memory is not shared
• cheap to create and destroy • completely isolated •
memory is not shared • communication over messages
• cheap to create and destroy • completely isolated •
memory is not shared • communication over messages • supervised (different strategies)
• cheap to create and destroy • completely isolated •
memory is not shared • communication over messages • supervised (different strategies) • distributed
sounds familiar?
sounds familiar? the actor model
garbage collector
• generational (old & new zones)
• generational (old & new zones) • collected per process
• generational (old & new zones) • collected per process
• no need if the process finished
• generational (old & new zones) • collected per process
• no need if the process finished • no global pauses
scheduler
• the BEAM creates 1 per core
• the BEAM creates 1 per core • memory is
not shared
• the BEAM creates 1 per core • memory is
not shared • perform load balancing
• the BEAM creates 1 per core • memory is
not shared • perform load balancing • guarantees that a process won't block others
BEAM
companies using the BEAM
• Whatsapp (2 million users/server)
• Whatsapp (2 million users/server) • Facebook
• Whatsapp (2 million users/server) • Facebook • Goldman Sachs
(High frequency trading)
• Whatsapp (2 million users/server) • Facebook • Goldman Sachs
(High frequency trading) • github (git proxy, gh-pages, gists)
• Whatsapp (2 million users/server) • Facebook • Goldman Sachs
(High frequency trading) • github (git proxy, gh-pages, gists) • heroku
• Amazon SimpleDB
• Amazon SimpleDB • RabbitMQ
• Amazon SimpleDB • RabbitMQ • CouchDB
• Amazon SimpleDB • RabbitMQ • CouchDB • Riak
really? using a 30 y/o tech?
it's under very active development
erlang 18 was released 30 days ago
why is the industry looking back?
telcos had tough constrains
we're experiencing problems that were solved 30 years ago
problems that were hidden by the Moore's Law
erlang in 1 minute
purely functional lang
data is immutable
powerful pattern matching
actor based concurrency
None
OTP Open Telecom Platform
huge repository of all kinds of libraries
• crypto
• crypto • http servers
• crypto • http servers • tcp servers
• crypto • http servers • tcp servers • realtime
distributed databases
• crypto • http servers • tcp servers • realtime
distributed databases • GUI and graphics
thanks!
questions?