Like I said before, the django admin can be huge time saver. On the other hand if you need to deal with concurrency or background tasks then Phoenix will be so much nicer to work with.
Also after working with Elixir and its functional nature it’s kinda tricky to go back to mutable classes. It’s really so easy to reason about your code in Elixir which helps tracking down bugs.
If you need dynamic or live-upating HTML views then Phoenix live view is also a very nice feature. Sure, it can be done with javascript + websockets, but there’s way more complexity involved!
And finally working with GraphQL is amazing in Elixir - especially in combination with subscriptions. In Django we had very bad experiences, like huge perfomance drops once the datasets reached a certain size. Absinthe (the GraphQL library for Elixir) on the other hand was very fast and stable, even with complex workloads. It also outperformed Apollo (a node.js implementation) in our tests on complex workloads (deep trees).
