Learn PHOENIX with Real Code Examples

Phoenix uses Elixir and the BEAM VM to provide fault-tolerant, concurrent, and low-latency web applications.

It follows the MVC architecture, with emphasis on functional programming and immutable data.

Built-in support for real-time features via Channels and PubSub.

Provides generators, Ecto for database interactions, and a templating system for views.

Hot code reloading and lightweight processes allow rapid development and highly concurrent systems.

Controllers, models, and views with MVC pattern

Ecto ORM and query DSL

Templating system (HEEx)

WebSockets and real-time channels

Functional programming with immutable data

Router - maps requests to controllers

Controller - handles request logic

View - renders templates (HEEx)

Template - HTML rendering system

Channel - real-time bi-directional communication

lib/ - application and web code

lib/my_app_web/ - controllers, views, channels

config/ - environment and database configuration

priv/ - static assets, templates, migrations

test/ - unit, controller, and integration tests

Define routes in `lib/my_app_web/router.ex`

Create controllers and actions

Define models and schemas using Ecto

Build views and templates with HEEx

Implement real-time features with Channels

Beginner: simple static pages with Phoenix templates

Intermediate: CRUD application with Ecto

Advanced: REST API with authentication and validation

Expert: real-time chat or notification system

Architect: distributed, fault-tolerant web platform

Phoenix vs Rails -> Phoenix is highly concurrent and functional; Rails is convention-heavy and synchronous

Phoenix vs Django -> Phoenix uses Elixir and BEAM concurrency; Django is Python-based and synchronous

Phoenix vs Laravel -> Phoenix is functional and real-time capable; Laravel is PHP-based with MVC

Phoenix vs Node.js frameworks -> Phoenix offers BEAM fault-tolerance and lightweight processes; Node.js single-threaded event loop

Phoenix vs Play -> Both JVM/BEAM frameworks; Phoenix is functional and uses Elixir, Play is OOP with Java/Scala

2014 - Phoenix initial release

2015 - Phoenix 1.0 stable release

2016 - Phoenix 1.2 adds Channels and LiveView previews

2017 - Phoenix 1.3 introduces contexts and project restructuring

2018 - Phoenix 1.4 improves Channels and PubSub

2019 - Phoenix 1.5 adds LiveView and HEEx templates

2020 - Phoenix 1.6 with OTP and LiveView enhancements

2022 - Phoenix 1.7 improves performance and real-time tools

2025 - Latest Phoenix release with enhanced LiveView, HEEx, and PubSub improvements

Controller - handles request logic

View - renders templates (HEEx)

Template - HTML rendering

Channel - WebSocket-based real-time communication

Ecto - ORM and database management