Skip to content
umlimator
Main Navigation GuideAPIExamples
Changelog
npm
Releases

Appearance

Sidebar Navigation

Examples

All examples

Maps

Map

UML structure

Class

Object

Package

Composite structure

Component

Deployment

Profile

UML behaviour

Use case

Activity

State machine

Sequence

Communication

Interaction overview

Timing

Information flow

SysML

Requirement

Block definition

Internal block

Parametric

Architecture, data and process

C4

Entity-relationship

Data flow

Flowchart

BPMN

Mindmap

Cloud architecture

AWS

Google Cloud

Azure

Atlas

The Umlimator Atlas

The Bookshop Atlas

Deployment diagram ​

A bookshop in production: the shopper's device and browser, an edge proxy, the shop's data centre with its application server, Java runtime and database host, and the order queue, with the artifacts deployed on them and the components they manifest. The page below opens on it, The bookshop in production, live: pan, zoom, select and go into the cards that stack.

Open full screen (Deployment)Conformance (Deployment)PDF (Deployment)Model (Deployment)

What it shows ​

In the order you find them in the picture:

  1. A device drawn as a cube with <<device>> over its name (Shopper's device, Application server)
  2. An execution environment nested in a device, <<executionEnvironment>> over its name (Web browser, Java 21 runtime)
  3. Artifacts deployed by nesting, <<artifact>> over the name with the document icon (storefront.js, order-worker.jar, shop-api.jar)
  4. A deployment line, dashed with an open arrowhead and <<deploy>> (routes.conf to the Edge proxy)
  5. A node with a stereotype over its name (<<linux server>> Edge proxy, Database host)
  6. Communication paths, plain solid lines with their protocols (HTTPS, HTTP, PostgreSQL wire protocol, AMQP)
  7. A node holding nodes, three levels deep, each drawn as a cube inside its owner (Shop data centre, Application server, Java 21 runtime)
  8. A deployment specification, <<deployment spec>> over its name (shop-api.yaml)
  9. A dependency, dashed with an open arrowhead (shop-api.yaml to shop-api.jar)
  10. A note linked to the deployment specification by a dashed line
  11. Manifestations, dashed with <<manifest>>, from an artifact to the component it makes (order-worker.jar to Order worker, shop-api.jar to Shop API)
  12. Components drawn with the component icon (Order worker, Shop API)
  13. A plain node outside the data centre, joined by a path from a nested device (Order queue)

In another setting ​

The same example, where a setting cannot share the picture above:

The same deployment, laid out right

Laid out right (direction left at its default) instead of down: the same nodes, artifacts and lines, with one pin (layout, the order queue at column 4) so no line crosses another.

Edit this page on GitHub
Pager
Previous pageComponent
Next pageProfile