chartletv0.21.0

← All examples

The platform layers, lifted apart

The same platform as the flat layer stack, its layers lifted apart as slabs in 2:1 dimetric projection at equal gaps, with dotted guides between their corners and the labels, items and notes at the side on leader lines. The description and table are those of the flat stack; on a phone-width canvas the stack is drawn flat. Illustrative platform.

The platform layers, lifted apart

examples/platform-exploded.json
{
  "schemaVersion": 1,
  "type": "layers",
  "title": "The platform layers, lifted apart",
  "source": "Platform team, architecture overview",
  "width": 960,
  "height": 640,
  "mobile": {
    "width": 420,
    "height": 640
  },
  "layers": {
    "projection": "exploded",
    "layers": [
      {
        "id": "infrastructure",
        "label": "Infrastructure",
        "items": [
          "Compute",
          "Storage",
          "Network"
        ],
        "note": "Rented from one provider; capacity is changed by the platform team only."
      },
      {
        "id": "runtime",
        "label": "Runtime and data",
        "items": [
          "Containers",
          "Message broker",
          "Relational database"
        ]
      },
      {
        "id": "services",
        "label": "Domain services",
        "items": [
          "Orders",
          "Catalog",
          "Billing"
        ],
        "note": "One team per service.",
        "role": "critical"
      },
      {
        "id": "experience",
        "label": "Experience",
        "items": [
          "Web shop",
          "Mobile app"
        ],
        "role": "planned"
      }
    ]
  }
}
Focus
The platform layers, lifted apart
The platform layers, lifted apartLayer stack of 4 layers, from the bottom: 1 Infrastructure (items: Compute, Storage and Network; note: Rented from one provider; capacity is changed by the platform team only.); 2 Runtime and data (items: Containers, Message broker and Relational database); 3 Domain services (items: Orders, Catalog and Billing; note: One team per service.); 4 Experience (items: Web shop and Mobile app). Roles: critical: Domain services; planned: Experience.Infrastructure: Rented from one provider; capacity is changed by the platform team only.Infrastructure· Compute· Storage· NetworkRented from one provider; capacity ischanged by the platform team only.Runtime and dataRuntime and data· Containers· Message broker· Relational databaseDomain services: One team per service.Domain services· Orders· Catalog· BillingOne team per service.!ExperienceExperience· Web shop· Mobile app+!Critical+Planned
The platform layers, lifted apartLayer stack of 4 layers, from the bottom: 1 Infrastructure (items: Compute, Storage and Network; note: Rented from one provider; capacity is changed by the platform team only.); 2 Runtime and data (items: Containers, Message broker and Relational database); 3 Domain services (items: Orders, Catalog and Billing; note: One team per service.); 4 Experience (items: Web shop and Mobile app). Roles: critical: Domain services; planned: Experience.Infrastructure: Rented from one provider; capacity is changed by the platform team only.InfrastructureRented from one provider; capacity is changed by the platformteam only.ComputeStorageNetworkRuntime and dataRuntime and dataContainersMessage brokerRelational databaseDomain services: One team per service.Domain servicesOne team per service.OrdersCatalogBilling!ExperienceExperienceWeb shopMobile app+!Critical+Planned

Source: Platform team, architecture overview

Show chart data
Data for The platform layers, lifted apart
LevelLayerItemsNotesRole
1InfrastructureCompute, Storage, NetworkRented from one provider; capacity is changed by the platform team only.
2Runtime and dataContainers, Message broker, Relational database
3Domain servicesOrders, Catalog, BillingOne team per service.critical
4ExperienceWeb shop, Mobile appplanned
  • Exploded layer stack
  • Show the levels of a system apart