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.

Wherever you do it you’ll have the same problem. If contexts can only make data changes in a way that transactionally composes, then they can’t be where your “business logic” is. I don’t see a difference in an application layer and a domain layer.

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

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

I don't use phoenix contexts like DDD bounded contexts. I see them as my domain layer and phoenix/web as the application layer. Depending on what kind of application I'm building, I'm pushing infra to the outside as well. In this specific case, cross domain context transactions can be done safely.

IMO context, the way they are advertised by generators, are way too small and granular for DDD bounded contexts. They are maybe modules, maybe aggregates, or maybe just don't fit in DDD patterns at all.

What is the difference between a domain layer and an application layer in your usage? I don’t typically see people use them as separate terms. They are typically synonyms.