ElixirConf: ElixirConf 2023 - Zach Daniel - Ash 3 0 Better Together
Comments welcome! View the elixirconf tag for more ElixirConf talks!
12 Likes
I believe this talk was a tipping point for many of us. Great talk!
Phoenix is a unique framework; itās not really a framework in the traditional sense found in other languages (donāt call us, weāll call you- kinda motto). Instead, itās just part of the user request and HTML rendering pipeline created by Plug. It doesnāt impose any specific opinions on how to structure, represent, or access data and business rules. This is particularly fantastic once you move beyond the āhello worldā stage (who hasnāt faced some challenges dealing with a frameworkās magic?).
Ash fitās right there, where phoenix tells you to write a context and do what ever you need or want.
I truly appreciate Elixir for how its tools are composable. In this case, you can seamlessly use one, two, or none of these tools to achieve your desired outcome.
6 Likes
Nice talk indeed. Thx!
Iām intrigued by the duality between regular Elixir code and SQL filters. Itās something Iāve tackled many times before, encoding business rules both in Elixir code and in queries. Where can I read more about that subject? Iāve found this: Expressions ā ash v2.15.17 but maybe there is a better resource when starting out fresh.
Right now that is probably the best resource that we have, but youāre definitely right about how our expressions aim to solve for that duality by being āportableā instead of running on a single data layer (I.e can be run in elixir, SQLite, Postgres).
