Phoenix for Rubyists

Introduction to Elixir and Phoenix

Transcript

1. Phoenix for Rubyists Concurrency and Scalability with Productivity by Doug Goldie Code Cauldron
2. Bunny Trails Learning something new…. Why are you here?
3. New Language/Framework Scalability Concurrency Multicore machines Productivity of Rails
4. Moore’s Law is Dead! number of transistors in a dense integrated circuit doubles approximately every two years. We are seeing more multi-core machines with more cores.
5. What do we build? Any Web Applications Distributed Systems But we still want productivity
6. Today Phoenix Elixir Erlang
7. Web Applications Classic CRUD monolith Single page app (SPA) - with any frontend Realtime app productivity and performance.
8. Distributed Systems Large-Scale distributed, fault-tolerant system Phoenix as the Web component Elixir for the other components. Small distributed apps. productivity and performance.
9. Agenda Elixir in 10 minutes Basic Phoenix app Real-time app Distributed systems Some really contrarian, disruptive ideas !!
10. Elixir
11. Elixir in 10 minutes placeholder
12. Basic Web Application
13. Phoenix demo Classic Rails example
14. Real-time Application
15. Real-time Features Phoenix Channels Topics Elixir & Erlang Massive concurrency Actor model Processes
16. Processes • lightweight, small memory, fast to create and terminate • message passing • no shared data • links and monitors • error handling Erlang is designed for massive concurrency
18. Chat demo Classic real-time example Phoenix channels / topics presence http://work.stevegrossi.com/2016/07/11/building-a- chat-app-with-elixir-and-phoenix-presence/
19. Distributed Systems
20. HTTP Server Nginx and Phusion Passenger Request processing Ruby on Rails Long-running requests Go Server-wide state Redis Persistable data Redis / MongoDB Background jobs Cron, Bash scripts, and Ruby Service crash recovery Upstart Erlang Erlang Erlang Erlang Erlang Erlang Erlang Server A Server B
22. Hard Problem to Solve
23. with only 10 engineers! In 2014, sold for $19 Billion. 465 million users 550 servers
24. Erlang History Developed over 25 years ago by Ericsson for building Telcom products Released as open source in 1998.
25. Requirements • high concurrency • distribution • fault tolerant • soft realtime • high availability • external interfaces • hot code upgrade
26. Processes • lightweight, small memory, fast to create and terminate • message passing • no shared data • links and monitors • error handling Erlang is designed for massive concurrency
27. Scheduler
28. OTP Library of Design Patterns Behaviors Client Server Supervisors and Workers
29. Gen Server
30. Lifecycle of GenServer
31. Fault-tolerance
33. Quotes “Best kept secret in software” 
 - Evan Miller, author of Chicago Boss “Erlang is about building Systems”
 - Robert Virding “Erlang makes the easy things hard 
 and the hard things easy”
34. Umbrella demo Phoenix and Elixir have Umbrella apps. Separate Applications in one repo.
35. Disruptive Ideas Service-Oriented Architectures MicroServices Web Services: json Front-end Frameworks? Are there better ways?
36. Review
37. Erlang review • massive concurrency • Processes • OTP • Virtual Machine (BEAM)
38. Elixir review • BEAM (Erlang VM) • modern syntax • macros • tooling • community • documentation
39. Phoenix review • pipelines • changesets • contexts • channels/topics • umbrella apps