Post

ecto queries in liveviews and controllers? discuss. 🍿 #ElixirLang #phoenix #code

I think they are totally fine. Most of these queries are driven by specific view requirements and there is no point in littering contexts with functions like get_five_recent_nonshipped_ordera_by_user. Context should be for "serious" business logic.

I actually posted about this recently, just not here. genserver.social/notice/Ap4or...

In your example, the problem with calling multiple context functions that not all context functions are guaranteed to be composable within a transaction. They have effects like broadcasting over pubsub, or ordering requirements etc.

So maybe contexts should not do that? Or wrap everything with an outbox pattern. In the end it really is the question if the context is part of the domain layer or application layer, I think.

I'm not sure I understand what you're saying. Why is business logic coupled with doing other things than transactional composition?

Not all applications have exactly one database for everything. Applications will integrate with external services etc. your user registration context function might do things like send emails and track analytics etc.

If you see contexts as something similar to DDD bounded contexts, then I agree, you should not do any cross context transactions, because all bets are off. In that case though it doesn't make sense to talk about an application or domain or infra layer, because a context contains potentially all 3