ozymandias
Hi everyone. I’m kind of new to the community and I just developed a small prototype for an internal system using phoenix. It’s just a bunch of CRUDs with a some business logic, and the docs made it really easy to build everything, but something is bugging me. At no point in the process I really had to think of OTP and the whole Elixir model. I normally start to learn by doing and dive into the concepts when they are needed, but it didn’t work in this case. My question is, did I just ignore some patterns I don’t know that I could have used, or does Phoenix really abstract away the OTP part for simple projects?
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kokolegorille
It abstracts a lot and You don’t need to learn OTP to use Phoenix.
But it’s everywhere, and liveview is a gen_server under the hood, so You can learn how to send messages from it.
If You have it activated, You can use :observer.start to see all the processes running, from the console.
Don’t forget to update extra_applications in mix.exs to run it, like this…
Welcome to Elixir
ozymandias
Got it. Thanks, I feel welcome
garrison
Phoenix hides a lot, but it’s there if you squint. As mentioned above, a LiveView is a GenServer and some of that leaks through (like the
handle_infocallbacks). LiveView’s async assigns make use of tasks and supervisors to perform work asynchronously and then send the result back as a message.OTP really comes into play if you embrace the ecosystem. If you use a library like
Cachex, for example, which builds on OTP to provide a Redis-like KV store. Or Phoenix’s own PubSub, which essentially provides fanout for message passing. What’s special about the BEAM is that all of these things can exist within the same runtime, built on top of the same abstractions.