From Front End to Full Stack with Elixir and Phoenix
summary
Claim: moving from front end to full stack with Elixir and Phoenix proves easier than expected by building a well-tested Phoenix API from scratch, borrowing ideas back into Ember (Ember ChangeSet). Uses Elixir, Phoenix, Plug, Ecto and Dialyxir, and follows JSON API conventions. Implements a reusable Terraform plug that forwards unmatched routes to a legacy API by catching missing-route errors so an incremental endpoint-by-endpoint rewrite works in production. Advises avoiding OOP patterns, preferring pipes, pattern matching and small composable functions.
AI-written summary · about
chapters (13)
- 0:00Start
- 8:44Recursion
- 10:03Add to accumulator
- 11:18Data Types
- 14:24Protocols
- 16:19Interface
- 17:34@spec
- 17:50Macros
- 22:32Phoenix is a pipeline
- 25:17Incremental Phoenix
- 26:59Terraform
- 28:57Design Patterns
- 31:44Model the System
related talks
39mBuilding beautiful systems with Phoenix contexts...
07mLightning Talk: A Backend Engineer's Vue of Front-End Development
36mBuilding Beautiful Systems with ...
32mShattering your application into an umbrella project
46mFrom a Ruby on Rails Monolith to Elixir and Elm Microservices
40mFRONTEND CHOICES
52mWhy Full-Stack Is the Future of Web Application Development
30mTales of Using Phoenix LiveView at an Early Stage Startup