Re: Integrating BCs - in real life

Hi Atle,

I am no expert but currently i am resolving the same issue. I ended up
using an event bus, with entities and handlers raising events, and event
handlers in other contexts subscribing to relevant events.

This way you can create local read models of relevant parts of other
domains in your local context (via handlers caching event info to a local
read model db). Imho since everything is decoupled and eventually
consistent, the nightmare is reduced (at the cost of a bit of
infrastructure).

If this hasnt been explained well (as i am new to DDD) let me know and i
can expand.

Regards

Chris
On 23 Apr 2013 00:00, "atle03" <[email protected]> wrote:

> **
>
>
> Hi all,
>
> If one application service in one bounded context (BC) needs to access the
> domain models for several BCs, how will this look like in the runtime
> environment?
>
> I see two alternatives:
>
> 1. The various BCs are hosted/deployed separately. In this case,
> operations on "remote" domain models could be accessed through (web)
> services or similar. A side effect is that transactions cannot span such
> remote operations, and that domain operations must be wrapped in a service
> layer. Web service hell?
>
> 2. The various referred domain models are deployed with the BC that refers
> to them. This means that calls are in-process. BUT this also means that the
> "host " BC must hold connection strings and optionally other config for all
> the domain models (repositories) it uses. Config hell?
>
> Both options seem to have large drawbacks to me. Is there something I have
> missed?
>
> Atle
>
>  
>