Learn web development with Elixir. We use GenServer Behaviour for a stateful backend. The front-end will use Phoenix Channels to communicate with the backend.

Functional Web Development with  Elixir, OTP and Phoenix by The Pragmatic Programmer_ .png

elixir_islands_test.tar.gz

elixir-app

pheonix-app

elixir-app-guesses

island-interface

phoenix-app-compiled

phoenix-app-iex

phoenix-app-form

phoenix-app-new-module

client-connection

presence

phoenix-app-final

without-presence

Elixir and OTP provide exceptional tools to build rock-solid backend applications that scale. In this course, you’ll build a web application in a radically different way, with a backend that holds application state. You’ll use persistent Phoenix Channel connections instead of HTTP’s request-response, and create the full application in distinct, decoupled layers.

In Part 1, you’ll start by building the business logic as a separate application, without Phoenix. You’ll model the application domain with Elixir functions and simple data structures.

In Part 2, you’ll add in the GenServer Behaviour to make managing in-memory state a breeze. 

In Part 3, you’ll build a web interface with Phoenix where you’ll use Phoenix Channels to establish persistent connections between the stateful server and a stateful front-end client.

Needless to say, you’re going to love this way of building web apps!

Functional Web Development with Elixir, OTP and Phoenix

## We’ve built a game!

Congratulations! We’ve made it.

We’ve built a Phoenix channel that provides an interface to the game engine we wrote in the first part of the course. We did it without coupling the logic to the interface in any way. The game engine concerns itself entirely with the business logic of the game. The Channel concerns itself entirely with brokering messages between clients and the game engine.
We’ve seen how to use Phoenix Presence to track clients who have subscribed to a channel on a topic and have also seen how to use that to implement an authorization scheme to join the Channel.

With that, we’ve completed the last layer we’re going to cover in this course. Now go build some amazing new web apps!

# We’ve built a game!

Congratulations! We’ve made it.

We’ve built a Phoenix channel that provides an interface to the game engine we wrote in the first part of the course. We did it without coupling the logic to the interface in any way. The game engine concerns itself entirely with the business logic of the game. The Channel concerns itself entirely with brokering messages between clients and the game engine.
We’ve seen how to use Phoenix Presence to track clients who have subscribed to a channel on a topic and have also seen how to use that to implement an authorization scheme to join the Channel.

With that, we’ve completed the last layer we’re going to cover in this course. Now go build some amazing new web apps!

Summarize what we learned in this course.

Introduction

Mapping Our Route

Model Data and Behavior

Working of State Machines

Add OTP for Concurrency and Fault Tolerance

Process Supervision for Recovery

Generate a New Web Interface with Phoenix

Create Persistent Connections with Phoenix Channels

Appendix

Wrapping Up

We’ve built a game!