pmjoe
Do you have any tips or links on how to structure a Elixir application? I’m keen towards a more feature based separation instead of type based (controllers, models, …). But I never did any big project in Elixir so everything is still a question for me.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
lccezinha
Maybe this topic can help you How to structure a large live view app? - #19 by eahanson
sodapopcan
Phoenix contexts are loosely based on Bounded Contexts from Domain Driven Design. DDD is a huge topic with many concepts but you don’t actually need to learn them all, you can pick and choose. I’ve worked in a company that successfuly employed DDD—bounded contexts were the part that clicked most for me (at least of the more in depth topics), so that was a big draw of Phoenix for me.
JEG2
Very loosely. I reread the docs two weeks ago and I feel like they’ve toned down some of the initial guidance. I would now summarize their main thrust as, “Don’t put business logic in your controllers.”
sodapopcan
Yes, indeed very loosely. I wouldn’t even say this is recent. This makes me realize I should have framed my comment more like: “If you wanna check out Bounded Contexts then maybe you’ll gain some insight into Chris’ thinking which you can then take or leave.” It’s what I get for checking Elixir Forum and trying to respond in the 5 mins before my rice was done cooking.
dimitarvp
Definitely. Ultimately all the stuff like “models”, “controllers”, “views” and what-have-you are just artifacts of our own imagination; artificial constructs that help us think about a problem better. But, hm, they don’t fit the brains of all of us that well though.
I’ve voiced ideas – one that I never acted on for now – that framework artifacts should live in entirely different directories even. Maybe one day I’ll try. Though with having a library like
boundariesthat becomes a semi-moot point.