As a (simple) alternative to graphical mapping with deployment diagrams (see tip 7-6 (deployment diagrams)), you could use tables to document or specify deployment of software on hardware.
| Server | Artifact | Remark |
|---|---|---|
| OneServer | A docker container, requiring at least Docker V 12.1 | |
| DomainServices | auto-deployed by Gradle build script | |
| OtherServer | Dell(c) Server, Quad-Core i7 CPU, 64GB RAM, running RH Enterprise Linux | |
| Articles | Unix executable, build by make, executed via cron | |
| FooBar | Java jar, build, deployed and executed via Gradle build script | |
| CassandraDB | Open source database, started via cron |
Please find the corresponding diagram below:
