Quick DDD terminology question: Say Context B depends on A (e.g. because B uses one of A’s services). Is A always “upstream”, or does this change depending on whether one applies “Conformist” or “Customer/Supplier”?
6
1
1
12
Btw the question phrasing seems odd, as you use "depends on" and "uses service" as synonyms. Runtime dependency is independent of model flow imho. B can call A, but if A conforms to B's model, B is upstream, A is downstream.
1
1
Don’t introduce the term “model flow” again, I carefully tried to avoid it ;) Of course run time and development time dependencies don’t have to map 1:1. Let’s just assume they do for this discussion.
1
1
But "dependency" is confusing: To me, in a context map, "B depends on A" would mean A drives change in B, e.g. A is upstream, B is downstream. But you seem to mean something else with "depends on".
1
That’s *exactly* what I wrote, though?!?
1
The point I was trying to make was this:
Also, dependency (I use your services) is not the definition of downstream. If I have the power to make you conform to the protocol I want to use when talking to your service, I am upstream.
1
Replying to @lutzhuehnken
While I agree with Eric (as per his authority, as he defined the terms), I still think you said the same thing I did and criticized me for saying it :) But we can take this offline.

Jun 22, 2018 · 4:26 PM UTC