Functional Web Development with Elixir, OTP, and Phoenix

Add a Web Interface with Phoenix

In Part 3, we’ll generate a new Phoenix application without Ecto, the database layer that ships with Phoenix. We’ll bring in our new Islands engine as a dependency and make it part of our new Phoenix application’s supervision tree. We’ll also see how to wire it up with the standard Phoenix MVC parts—the router, a controller, a view, and some templates.

Then we’ll move on to the really exciting part: replacing HTTP’s temporary client-server connections with persistent ones via Phoenix channels. Channels provide a conduit for lightning-fast message passing between front-end applications, and in our case, a stateful back-end server. We’ll make good use of channel naming conventions to allow two players to connect ...