Checkout: the calls in order
Five connections of a checkout, numbered 1 to 5 in front of their labels. The description lists the steps in order with where each one goes, and a step number is used once. Laid out top down, so that the numbers read like a sequence. Illustrative values.
Checkout: the calls in order
examples/checkout-calls.json{
"schemaVersion": 1,
"type": "architecture",
"title": "Checkout: the calls in order",
"source": "Architecture handbook, runtime view",
"width": 900,
"height": 640,
"architecture": {
"components": [
{
"id": "customer",
"label": "Customer",
"kind": "person"
},
{
"id": "web",
"label": "Web shop",
"kind": "frontend"
},
{
"id": "api",
"label": "Shop API"
},
{
"id": "pay",
"label": "Payment provider",
"kind": "external"
},
{
"id": "db",
"label": "Orders",
"kind": "database"
},
{
"id": "mail",
"label": "Mail service",
"kind": "external"
}
],
"connections": [
{
"from": "customer",
"to": "web",
"label": "confirms the cart",
"step": 1
},
{
"from": "web",
"to": "api",
"label": "places the order",
"technology": "HTTPS",
"step": 2
},
{
"from": "api",
"to": "pay",
"label": "charges",
"technology": "HTTPS",
"step": 3
},
{
"from": "api",
"to": "db",
"label": "stores the order",
"technology": "SQL",
"step": 4
},
{
"from": "api",
"to": "mail",
"label": "sends the receipt",
"step": 5,
"dash": "dashed"
}
],
"mainPath": [
"customer",
"web",
"api",
"db"
],
"orientation": "portrait"
}
}Focus
Source: Architecture handbook, runtime view
Show chart data
| Component | Kind | Connects to |
|---|---|---|
| Customer | person | Web shop (step 1, confirms the cart) |
| Web shop | frontend | Shop API (step 2, places the order, via HTTPS) |
| Shop API | service | Payment provider (step 3, charges, via HTTPS), Orders (step 4, stores the order, via SQL), Mail service (step 5, sends the receipt) |
| Payment provider | external system | |
| Orders | database | |
| Mail service | external system |