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.
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!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
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
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
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted”
Version...
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
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
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
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
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
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










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.