Phoenix Framework

Overall view of Phoenix Framework.

Transcript

1. A HIGHLY CONNECTED WEB FRAMEWORK Pedro Assumpcao Raise Conf • 01/30/2015
2. • DEVELOPED WITH ELIXIR BY CHRIS MCCORD; • TOP LAYER OF A MULTI-LAYER: • PHOENIX; • PLUG (MIDDLEWARE); • COWBOY (HTTP SERVER). OVERVIEW
3. • ROBUST ROUTING; • WEBSOCKET AND PUB/SUB LAYER; • PLUG-BASED ROUTES AND CONTROLLERS; • PRECOMPILED VIEW LAYER. FEATURES
4. • DISTRIBUTED WEB SERVICES FRAMEWORK; • SIMPLIFY THE USE OF WEBSOCKETS, REAL TIME EVENTS AND SOA; • NO PRODUCTIVITY SACRIFICES FOR PERFORMANCE; • NO PERFORMANCES SACRIFICES FOR PRODUCTIVITY. GOALS
5. • CLONE PHOENIX GIT REPO; • FETCH DEPENDENCIES; • COMPILE. SETTING UP
6. • AFTER PHOENIX IS SET UP, A MIX TASK IS AVAILABLE TO CREATE APPS; • FETCH DEPENDENCIES; • COMPILE; • START SERVER. CREATING A NEW APP
7. • ROUTES; • CONTROLLERS; • VIEWS; • TEMPLATES; • CHANNELS. LET'S SEE WHAT WE GOT
8. ROUTES
9. get “/pages/:slug”, PageController, :show # GET /pages/about # [“pages”, “about”] def match(conn, “GET”, [“pages”, slug]) do Controller.peform_action(conn, PageController, :show, slug: slug) end get “/files/*path”, FileController, :show # GET /files/Users/pedro/Documents # [“files”, “Users”, “pedro”, “Documents"] def match(conn, “GET”, [“files” | path]) do Controller.peform_action(conn, FileController, :show, path: path) end ROUTES
10. CONTROLLERS
11. • VIEWS SERVER AS A PRESENTATION LAYER; • VIEWS RENDER TEMPLATES; • TEMPLATES ARE PRECOMPILED INTO VIEWS; • EEX AND HAML ENGINE SUPPORT; VIEWS AND TEMPLATES
12. VIEWS # web/views/page_view.ex defmodule HelloPhoenix.PageView do use HelloPhoenix.View ! def message do "Hello from the view!" end end
13. # web/templates/layout/application.html.eex <html> ... <body> <%= @inner %> </body> </html> ! # web/templates/page/show.html.eex <p>This is the message: <%= message %></p> TEMPLATES
14. • DEFINED IN THE ROUTER; • WEBSOCKET/PUBSUB ABSTRACTION; • PHOENIX.JS AS BROWSER CLIENT. CHANNELS
15. Elixir: www.elixir-lang.org Phoenix: www.phoenixframework.org RESOURCES
16. THANKS!