Wrapping Up
We’ve done a lot in this chapter in a short amount of time. We created a new project for our web interface. We brought the game logic in as a dependency, and we got the interface to call into the game server.
That’s the surface-level view. Looking at it more deeply, we’ve solved one of the most vexing problems related to using web frameworks. We’ve created a clean separation between logic and interface that will make testing and maintaining our application a breeze. If we ever need to upgrade to a newer major version of Phoenix, it’ll be a much, much easier task than it would be with other frameworks.
At this point, we’re ready to tackle one of the most exciting parts of Phoenix—channels. Channels provide persistent, stateful connections ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access