Model responsibility before location

An application or application component represents identifiable software responsibility: it implements behaviour, holds logic and has an owner and lifecycle. A hosting resource explains where that software runs. The distinction matters when a workload moves from one runtime to another without changing the business capability or logical application it supports.

Keep the service distinct from the implementation

An application service is behaviour offered to a consumer. One or more software components may realise that behaviour, and one or more interfaces may expose it. An API is an interface or contract; an API gateway is delivery technology. Collapsing all of these into a single application record obscures who provides the behaviour and what can change independently.

Try the replacement test

Ask what would happen if the runtime were replaced. If you moved from one compute service to another, would your business-facing software responsibility still exist? If so, the hosting choice belongs in the technology view. If the transformation logic itself were replaced or retired, that may be a logical application or component lifecycle event.

A practical example

Imagine a location-lookup function. A logical address-lookup component validates a request, applies mapping rules and calls an external provider. It is hosted on a managed runtime and reached through an API gateway. Describe the component, its exposed service, the API contract and the runtime separately, then relate them. This makes changing the gateway or compute platform a technology decision rather than an accidental application retirement.

The architectural payoff

Separate records can feel like extra effort until the first migration. Then the model can answer four different questions accurately: what behaviour exists, which implementation provides it, how consumers access it and which technology runs it.

The MétiArch perspective

Strong architecture practice depends on precise models, explicit ownership and decisions that remain useful as systems change. Examples are fictional and are presented as architectural guidance.

← Explore all insights