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

## Allow the players to guess coordinates
Guessing coordinates is the most important action in the game. In order to process a guess, we need to know which player is guessing. We also need to know the row and column values the player is guessing.

We start with a client function, `guess_coordinate/4`, that takes those values. This wraps a `GenServer.call/2` with a tuple representing the four arguments and the action. We can see this here:
```Elixir
def guess_coordinate(game, player, row, col) when player in @players, do:
  GenServer.call(game, {:guess_coordinate, player, row, col})
```

# Allow the players to guess coordinates
Guessing coordinates is the most important action in the game. In order to process a guess, we need to know which player is guessing. We also need to know the row and column values the player is guessing.

We start with a client function, `guess_coordinate/4`, that takes those values. This wraps a `GenServer.call/2` with a tuple representing the four arguments and the action. We can see this here:
```Elixir
def guess_coordinate(game, player, row, col) when player in @players, do:
  GenServer.call(game, {:guess_coordinate, player, row, col})
```

Understand the functionality of guessing a coordinate.

Guess a Coordinate

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

Guess a Coordinate

Allow the players to guess coordinates