wolfiton
Context separation or decoupling conventions and naming
Hi everyone,
Explanation:
This questions is created to establish the best way to deal with separation of big context like a blog in smaller pieces.
The main problem is that a Blog context can get very big if all the schemas go under one context.
Problem:
I wanted to ask if the what is your opinion on the following scenario:
Article context with schema Article and a migration Articles
This would look something like this
YourApp.Article.Article when you will need to reference the schema which might be confusing
So I thought of making the naming more descriptive like this:
YouApp.ArticleContext.ArticleSchema
Question: Is there a better way to name this modules: context and schema for easy readability?
Thanks
Most Liked
baldwindavid
This post helped me in trying to organize contexts… https://devonestes.herokuapp.com/a-proposal-for-context-rules
baldwindavid
I do something similar for the blog part of my app, though your contexts are sliced thinner than mine.
MyApp.Blogging.Articles.Article
Blogging is the context
Articles is the sub-context
Article is the schema
All of the functions related to articles are in Articles.
The Blogging context then delegates to those functions…
alias MyApp.Blogging.Articles
defdelegate list_articles, to: Articles
defdelegate get_article!(id), to: Articles
...
LostKobrakai
For the question of where to separate things out I usually think about: Which things change together or independently (in the future). Which changes to a part of the system require changes to another part of the system (coupling). It a context is one cohesive part of your domain, but you feel it’s to big, first try to separate stuff within the context, before you move things out to their own contexts and them effectively becoming a part of your whole apps api.
Popular in Discussions
Other popular topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Real-time error tracking, performance insights, and observability for devs.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
Courses that'll move you from confusion to "Aha, now I get it!"