How artifacts realise application components and deploy onto nodes The Implementation and Deployment viewpoint traces each application component down to the artifacts that realise it and each artifact down to the node it runs on, so an artifact with no node cannot ship and a node holding every artifact reads as a concentration risk.
How artifacts realise application components and deploy onto nodes
A three-tier realise-then-deploy flow for London Grid Distribution, read top to bottom with a left axis marked logical to physical. The top tier holds two application components: the Meter data service and the LTDS publication system. Blue arrows labelled realises point up from three artifacts: the meter-ingest image realises the Meter data service, the ltds-api image realises the LTDS publication system, and the capacity schema also realises it. Blue arrows labelled deploys on point down: the two images land on the Kubernetes platform inside the Azure region node, and the capacity schema lands on the PostgreSQL cluster. Derived from the ArchiMate 3.2 Specification, The Open Group.
Application components Artifacts that realise them Nodes they deploy on
Logical to physical
realises deploys on Meter data service Collects half hourly reads. Component LTDS publication system Publishes the statutory tables. Component meter-ingest image Container image, ingest. Artifact ltds-api image Container image, the API. Artifact capacity schema Relational schema, headroom. Artifact
Azure region
Node
Kubernetes platform
Node
PostgreSQL cluster Managed database service. Node Derived from the ArchiMate 3.2 Specification, The Open Group
