Phoenix Framework for the realtime web
•
2 likes•195 views
This document provides an overview of the Phoenix Framework, which is a web framework built on top of the Erlang VM. It discusses how Phoenix was inspired by WhatsApp's use of Erlang to handle millions of real-time connections. Phoenix focuses on real-time communication through channels and provides easy abstractions for building concurrent, distributed, and fault-tolerant web applications. It aims to improve both short-term and long-term productivity for developers.
Recommended
More Related Content
Similar to Phoenix Framework for the realtime web
Similar to Phoenix Framework for the realtime web (20)
Recently uploaded
Recently uploaded (20)
Phoenix Framework for the realtime web
- 1. Phoenix Framework for the realtime web Pedro Medeiros
- 2. Summary
- 3. Summary ● Erlang model ● Brief Elixir ● Phoenix motivation ● Phoenix Channels
- 5. Erlang ● Created in 1986 ● Solves a specific Hard problem at the time ● Limited Resources ● In Brief ○ Fault-Tolerance ○ High Disponibility ○ Concurrent Oriented
- 7. Erlang ● Achievements ○ No shared state concurrency focused ○ Live code reloading ○ Clustering through message passing (Actor Model) ○ High Availability 99.9999999 % (nine Nines) ○ Used in GPRS, 3G and LTE networks worldwide
- 8. Erlang
- 12. 2 Million connections on a single node https://blog.whatsapp.com/196/1-million-is-so-2011?
- 18. Elixir ● Functional Programming language. ● On top of Erlang VM ● Immutable structures ● Concurrent ● Distributed ● Fault Tolerant
- 19. Elixir ● Design Goals ○ Extensibility ○ Productivity ○ Compatibility
- 20. Elixir ● Extensibility ○ Ad hoc Polymorphism (data type) ○ Strict and lazy enumeration APIs ○ Macros for metaprogramming
- 21. ● Macros Elixir
- 22. ● Macros Elixir
- 23. Elixir ● Productivity ○ Out of the box tools to startup a project ○ Nice syntax for test and documentation ○ Easy to distribute and to create libs
- 25. Elixir ● Compatibility ○ Compiles to ErlangVM ○ Elixir runs Erlang code Erlang runs Elixir code ○ Community grown
- 26. ● Calling Erlang from elixir ● Calling Elixir from Erlang Elixir
- 27. ● Exchange Code between those two. Elixir
- 28. Disclaimer
- 29. Elixir is not about a better syntax for the Erlang VM
- 30. 2 Million connections on a single node https://blog.whatsapp.com/196/1-million-is-so-2011?
- 32. Phoenix ● Started with Phoenix Channels ○ Inspired by the whatsapp case ○ Real time communication ○ Beyond browsers (native apps and IoTs)
- 33. Phoenix Easy Abstraction in javascript
- 36. PubSub Phoenix client server Channels socket.connect() Distributed Erlang Redis Postgres? XMPP? - Isolated - Concurrent
- 37. The road to 2 million connections
- 38. ○ 40 core 128 gb Rack space machine ○ Accomplish it with minor changes. Phoenix http://www.phoenixframework.org/blog/the-road-to-2-million-websocket-connections
- 39. Phoenix The road to 2 million connections
- 40. Phoenix Benchmarks "There are three kinds of lies: lies, damned lies, and statistics." - Clarisse Linspector
- 41. Phoenix Benchmarks $ wrk -t20 -c100 -d30s --timeout 2000 https://github.com/mroth/phoenix-showdown Library Throughput (req/s) Latency (m/s) Plug (elixir) 198 328 0.63 Phoenix (elixir) 179 685 0.61 Gin (go) 176 156 0.65 Play (scala) 171 236 1.89 Express Cluster (node) 92 064 1.24 Martini (go) 32 077 3.35 Sinatra (ruby) 30 561 3.50 Rails (ruby) 11 903 8.50
- 44. Productivity
- 45. Short term productivity vs Long term productivity
- 46. Short term productivity ● Great documentation as first class citizen ● Guides ● Code generators (as a learning tool) ○ mix phx.gen.html ○ mix phx.gen.json ○ mix phx.gen.channel
- 47. Short term productivity ● HTML Form Builders ● Great live code reloading ● Assets build tools with ES6 as default ● Pretty error pages ● First Class concurrent test tools
- 48. Long term productivity ● OTP Applications ○ Functional Programming ○ Introspection ○ Monitoring ○ Fault Tolerant ○ Supervisors ○ Visibility of application state
- 50. Wrapping up
- 51. Thanks ;)