Integrations

Connect the Domain to the Outside World

Real businesses do not operate in isolation.

They depend on payment providers, communication services, enterprise systems, identity providers, data sources, external APIs and operational platforms.

HexaKernel provides a foundation for connecting those systems to the domain.

Integrations as Capabilities

An integration should provide a capability to the domain without forcing the domain to become dependent on the implementation details of the external system.

The business thinks in terms of:

Send a notification.

Process a payment.

Create a document.

Retrieve customer information.

Update an external record.

The integration handles the technology required to make that capability happen.

Keep External Complexity Outside

External platforms change.

Providers change their APIs.

Services are replaced.

New systems become available.

The domain should not need to change simply because an implementation changes.

This separation keeps the business model independent from the technology landscape around it.

Integrations Under the Kernel

Integrations operate within the same execution context as the rest of the domain.

That means actions can remain connected to identity, permissions, events, audit and observability.

The result is not a collection of disconnected connectors.

It is a domain that can interact with the world while remaining coherent internally.

Connect anything the domain needs without making the domain depend on how it is connected.