Phoenix Framework
3 likes1,033 views
The document outlines the capabilities and performance of the Phoenix framework, leveraging the Elixir programming language for building concurrent applications. It highlights its use of channels for real-time communication, showcasing example code for user interactions and messaging. Additionally, it compares Phoenix's performance metrics with other web frameworks and emphasizes its productivity features such as generators and introspection tools.
![defmodule Chat.LobbyChannel do
use Phoenix.Channel
def join("chat:lobby", message, socket) do
broadcast! socket, “user_joined”,
%{username: message[“username"]}
{:ok, socket}
end
def handle_in("new_message", message, socket) do
broadcast socket, "new_message",
%{content: message["content"],
username: messages[“username"]}
socket
end
end](https://image.slidesharecdn.com/phoenix-160328143401/85/Phoenix-Framework-9-320.jpg)
Phoenix Framework
- 2. Glossary • Phoenix (web framework) • Elixir (programming language) • Erlang VM
- 4. http://blog.whatsapp.com/index.php/ 2012/01/1-million-is-so-2011/ 2 million connections on a single node
- 5. Intel Xeon CPU X5675 @ 3.07GHz 24 CPU - 96GB Using 40% of CPU and Memory
- 7. var socket = new Phoenix.Socket("/ws"); socket.connect(); var channel = socket.channel(“chat:lobby"); channel.on("user_joined", function(message){ // ... }); channel.on("new_message", function(msg){ // ... }); $input.on("enter", function(e){ channel.push("new_message", { content: $input.val(), username: App.username }); }); channel.join();
- 8. defmodule Chat.UserSocket do use Phoenix.Socket channel "chat:lobby", Chat.LobbyChannel channel "room:*", Chat.RoomChannel # def connect(params, socket) # def id(socket) end
- 9. defmodule Chat.LobbyChannel do use Phoenix.Channel def join("chat:lobby", message, socket) do broadcast! socket, “user_joined”, %{username: message[“username"]} {:ok, socket} end def handle_in("new_message", message, socket) do broadcast socket, "new_message", %{content: message["content"], username: messages[“username"]} socket end end
- 10. Server Browser Native Mobile Embedded Device “Browser" (IE) Outsideview Server
- 11. Insideview Client Server Transport socket.connect() Channels socket.join(channel) Pubsub • Distributed Erlang • Redis • PostgreSQL? • XMPP? • Isolated • Concurrent
- 13. htop
- 16. Performance
- 18. Library Throughput (req/s) Latency (ms) 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 $ wrk -t20 -c100 -d30S --timeout 2000 https://github.com/mroth/phoenix-showdown
- 19. Insideview Client Server • Isolated • Concurrent /users /users / /admin /search?q=elixir
- 20. IsolatedandConcurrent • Crashes are isolated • Data is isolated (GC is per process, no global pauses) • Load balances on IO and CPU (efficient on multicore)
- 21. Productivity
- 22. Productivity • Short-term productivity • Documentation / Guides • Workflows / Generators • Long-term productivity • Introspection • Maintainability
- 25. Generatorsaslearningtools $ mix phoenix.gen.html $ mix phoenix.gen.json $ mix phoenix.gen.channel
- 26. More… • Form builders • Static build tools with ES6 as default • Live reloading • Pretty error pages • First-class concurrent test tools • Packages via hex.pm
- 29. Applications • Package and run our code • Can be started and stopped as a unit • Provide unified configuration • Hold processes and state in the supervision tree
- 30. ObserverDemo
- 31. Applications • Introspection & Monitoring • Visibility of the application state • Easy to break into "components" • Reasoning when things go wrong
- 32. Summingup
- 35. elixir-lang.org