Infrastructure to enable integration of bounded contexts with messaging and web services

1
votes

On my first foray into integration of systems have I identified the following bounded contexts:

  1. Invoicing
  2. Subscriptions
  3. Collections

Specifically for the Collections bounded context 'suspends overdue accounts' feature, we would:

  1. Get a list of overdue invoices from Invoicing
  2. Send suspension notice to user (internal e-mailer service)
  3. Send suspension requested to Subscriptions bounded context

I understand how a blocking web service could be used to integrate the bounded contexts, but I can see this would bring issues in the event the remote service is down.

I am aware of message buses, but not sure how we would integrate with a message strategy:

Would each context contain a local read-model of external bounded context (listen for events from external bounded contexts when they are adding/deleting entities, and correlating via a unique ID)?

If using messages, do we literally build up a local copy of the entity (with fields of use for the local context) from the remote context of interest? Or am I missing something else?

1
domain-driven-designbounded-contexts
MEssage Driven Architecture, more exactly the Domain Events pattern is for this problem. A bounded context will sotre only relevant data for its own context i.e not a copy of what other BC considers to be the model. Your 'question' is too localized and quite debatable - MikeSW

1 Answers

1
votes

In your scenario, you can employ an event-driven architecture and avoid storing data locally. In order to suspend overdue accounts, you can have the Invoicing BC publish an event indicating that an invoice is past due. The Collections and Subscriptions BC would subscribe to that event and invoke the required behaviors. From the perspective of the Invoicing BC, you'd have a domain event called something like InvoiceBecamePastDue and it would be published externally via message bus.

In this case, it doesn't seem like you need a local copy. There are instances however where a local copy of data is required in which case you would maintain the local copy using published events.