Skip to content
ArchiMate templates

ArchiMate — Grouping and Location Across Two Regions

Where things run, which is a compliance question before it is an architecture one. Location and grouping are the two elements that belong to no layer, and this model uses them to say which components sit in which jurisdiction and what crosses between them.

Template previewArchiMate
Two-region deployment and what crossesArchiMate 3.2 · 11 elements · 16 relationships · 3 layersAPPLICATIONTECHNOLOGYOTHEROrder API (EU)Order API (US)Analytics platformEU order dataUS order dataAggregated metricseu-central-1 clusterus-east-1 clusterEuropean UnionUnited StatesRegulated datacounts only, no personal …counts only, no personal …NOTATION IN THIS VIEWApplicationTechnologyOtherAggregationAssignmentAccessFlowEvery line read — 11 elements and 16 relationships drawn.

Make it your own.

title "Two-region deployment and what crosses"

location EU  "European Union"
location US  "United States"
grouping Reg "Regulated data"

layer application
  application-component EuApi  "Order API (EU)"
  application-component UsApi  "Order API (US)"
  application-component Analytics "Analytics platform"
  data-object           EuOrders  "EU order data"
  data-object           UsOrders  "US order data"
  data-object           Metrics   "Aggregated metrics"

layer technology
  node EuCluster "eu-central-1 cluster"
  node UsCluster "us-east-1 cluster"

EU aggregates EuApi
EU aggregates EuOrders
EU aggregates EuCluster
US aggregates UsApi
US aggregates UsOrders
US aggregates UsCluster
US aggregates Analytics

Reg aggregates EuOrders
Reg aggregates UsOrders

EuApi assigned-to EuCluster
UsApi assigned-to UsCluster
EuApi accesses    EuOrders
UsApi accesses    UsOrders

EuOrders flows-to Metrics : counts only, no personal data
UsOrders flows-to Metrics : counts only, no personal data
Analytics accesses Metrics