chartletv0.21.0

← All examples

The layers of the platform, from the machine up

Four levels of a platform from the infrastructure up, each a band with its parts as small boxes that wrap onto rows, notes in a column at the side joined by a dotted line, and two roles — critical and planned — with a badge and an outline pattern. The description reads the layers from the bottom, the table has one row per layer with its level. With a phone variant, where the notes move under the labels. Illustrative platform.

The layers of the platform, from the machine up

examples/platform-layers.json
{
  "schemaVersion": 1,
  "type": "layers",
  "title": "The layers of the platform, from the machine up",
  "source": "Platform team, architecture overview",
  "width": 860,
  "height": 600,
  "mobile": {
    "width": 360,
    "height": 640
  },
  "layers": {
    "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",
          "Object store"
        ]
      },
      {
        "id": "services",
        "label": "Domain services",
        "items": [
          "Orders",
          "Catalog",
          "Billing",
          "Customers"
        ],
        "note": "One team per service; services talk only through published interfaces.",
        "role": "critical"
      },
      {
        "id": "experience",
        "label": "Experience",
        "items": [
          "Web shop",
          "Mobile app",
          "Partner API"
        ],
        "note": "The partner API is planned for next year.",
        "role": "planned"
      }
    ]
  }
}
Focus
The layers of the platform, from the machine up
The layers of the platform, from the machine upLayer 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, Relational database and Object store); 3 Domain services (items: Orders, Catalog, Billing and Customers; note: One team per service; services talk only through published interfaces.); 4 Experience (items: Web shop, Mobile app and Partner API; note: The partner API is planned for next year.). Roles: critical: Domain services; planned: Experience.Infrastructure: Rented from one provider; capacity is changed by the platform team only.InfrastructureComputeStorageNetworkRented from one provider; capacityis changed by the platform teamonly.Runtime and dataRuntime and dataContainersMessage brokerRelational databaseObject storeDomain services: One team per service; services talk only through published interfaces.Domain servicesOrdersCatalogBillingCustomers!One team per service; services talkonly through published interfaces.Experience: The partner API is planned for next year.ExperienceWeb shopMobile appPartner API+The partner API is planned for nextyear.!Critical+Planned
The layers of the platform, from the machine upLayer 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, Relational database and Object store); 3 Domain services (items: Orders, Catalog, Billing and Customers; note: One team per service; services talk only through published interfaces.); 4 Experience (items: Web shop, Mobile app and Partner API; note: The partner API is planned for next year.). 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 theplatform team only.ComputeStorageNetworkRuntime and dataRuntime and dataContainersMessage brokerRelational databaseObject storeDomain services: One team per service; services talk only through published interfaces.Domain servicesOne team per service; services talk only throughpublished interfaces.OrdersCatalogBillingCustomers!Experience: The partner API is planned for next year.ExperienceThe partner API is planned for next year.Web shopMobile appPartner API+!Critical+Planned

Source: Platform team, architecture overview

Show chart data
Data for The layers of the platform, from the machine up
LevelLayerItemsNotesRole
1InfrastructureCompute, Storage, NetworkRented from one provider; capacity is changed by the platform team only.
2Runtime and dataContainers, Message broker, Relational database, Object store
3Domain servicesOrders, Catalog, Billing, CustomersOne team per service; services talk only through published interfaces.critical
4ExperienceWeb shop, Mobile app, Partner APIThe partner API is planned for next year.planned
  • Layer stack
  • Show the levels of a platform