architecture - Should the Domain ever access Application Services of another system? -


spefically across 2 systems: can domain of system call application services/remote facade of system b?

for example if ordering system has order entity in domain, should validation method of order entity call applicaion service of stock keeping service check there enough product in stock fulfil order?

my instinct not correct way of doing things.

this simplified version of previous, rather convoluted question: integration between various domain driven design systems not nessacery or advised refer previous question.

first of all, pay consider architecture. why necessary domain logic hooks domain directly? can not consume data other domain publishes? if not, talking 2 disjoint domains, or part of same bounded context?

it may other system closed one, cannot extend it. may that other system not publish data based on events, , can access through api. in case, best use agent in domain model. is, domain logic should contain agent (proxy) connects remote system acts it's local. encapsulates fact actual logic/data not local.


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -