Skip to main content

Domain Integration Map

The Domain Integration Map (see demo) is a powerful visualization feature in EventCatalog that provides a high-level view of your domains, services and messages. It displays domains containing their services, with cross-domain message flows clearly visualized as connections between domains.

Example

This feature is particularly valuable for organizations practicing Domain-Driven Design (DDD) and event-driven architecture, where understanding the interactions between domains is crucial for system design and evolution.

How it works?

EventCatalog will visualize messages that are being sent between domains in EventCatalog.

As you write domains, services and messages in EventCatalog, some of these communications will be cross domain and boundary. This can be intentional or accidental.

Using the Domain Integration Map, you can see these cross-domain communications and understand the dependencies between domains.

How to see the Domain Integration Map

To see the Domain integration map, you need at least one domain in your EventCatalog.

  1. Click on the Visualizer button in the navigation bar.
  2. Click on the Domain Integration Map section.

You can a demo of the Domain Integration Map in the EventCatalog Demo.

FAQ

Why isn't it called a bounded context map?

It's very similar to a bounded context map, but it really depends on how you define domains and bounded contexts. Domains in EventCatalog are ways of grouping and organizing your services and messages. Some folks are using these as bounded contexts, but we are using them as domains.

To keep things simple (we think?) we are calling it a domain integration map.