or subscribe with
Join 3,000+ readers for one email each week.
Digests » 89
AppSignal: Elixir’s first error monitoring and performance tool
this week's favorite
I've been doing a personal project on the side for a while now, and it has a web API component, which I wrote in Phoenix 1.2. That was my first time using Phoenix on a serious project that I intend to ship.
Suppose we are making a multi-player game. We are choosing to store the state of the game in a struct (Game). The game will start without any players and players will individually choose to join the game. We’ve determined that there must be a maximum number of players (@max_players) and the players will be represented by a list of strings (player nicknames).
Today, I want to talk a little bit more about a killer combo I've uncovered: action_fallback + contexts. I'm still amazed at how Phoenix 1.3 enables my controllers to be so tiny.
Elixir Daze is considered (by the organizers) a more regional conference, but if you take the line up you will notice that is not that true, the talks are in an excellent level for subjects that matter, with the presence of some well known people from the community like Dave Thomas, Francesco Cesarini and Saša Jurić.
Elixir gives you the tools to easily write concurrent code. In an earlier post, I introduced concurrency in Elixir by looking at the building blocks of concurrency. Processes follow the actor model of concurrency and are the core underlying construct with which you can then send and receive messages between other processes.