Start with the logical application

An application or application component represents software that performs work. It has functional responsibility and a lifecycle, regardless of which hosting platform runs it. The cloud function hosting that logic is a technology choice, not necessarily the application's architectural identity.

An integration describes interaction

When two applications interact, an integration record captures the structural relationship. Its integration type can be API, event, messaging, file transfer or another agreed mechanism. This is separate from the contract that specifies exchanged information.

An API records a contract

For API integrations, model the API as a distinct artefact and reference the authoritative OpenAPI contract where one exists. Keeping contracts separate from the integration relationship avoids confusing 'who communicates' with 'how a request and response are defined'.

A service represents exposed behaviour

An application service is behaviour offered for others to use. One or more application components may realise that service. An API may expose it, but service, API and application should not automatically be collapsed into one element.

Why these boundaries matter

Distinct identities support clearer change impact, ownership, reuse and ArchiMate-aligned modelling. They also let an architect vary the hosting technology without accidentally changing the logical meaning of the application or its published service.

The MétiArch perspective

Explore more MétiArch Insights for practical architecture perspectives.

← Explore all insights