Programmer and life long iconoclast
Stateful Web Apps with Phoenix and OTP
The Phoenix Framework offers an extensive set of tools to write stateless web applications, similar to what you find in Ruby on Rails. Phoenix provides straightforward ways route HTTP requests, read and save data from a database, and generate JSON and HTML. But while it's great to have the tools you're comfortable with, it's easy to ignore the most powerful tool in the Elixir/Erlang ecosystem - the OTP. OTP opens up a whole new model of web programming where you track state directly in your application, instead of calling out to a database. Now the question is -- how and when do you use this tool? And is it even a good idea to do so? What use cases are better suited to OTP than a database? What is OTP's relationship to to Phoenix’s realtime tools like Channels and Presence? And how might you mix database models with OTP tools inside a single web application? We'll look at this wide open new world of stateful web applications and try to chart a path through together.
Hannah Howard is a senior developer and tech generalist with over 15 years experience in programming and other technical fields. Prior to programming, Hannah worked for 10 years in the non-profit sector in Los Angeles, specializing in LGBT advocacy and community organizing. Hannah returned to coding in 2012, and brings her passion and experience from community organizing to helping new programmers get up to speed on technical topics.Twitter: @techgirlwonder