是否存在用于记录或说明(Docker)容器在系统体系结构规范中的作用的公认的UML图表样式? [英] Is there an agreed UML diagram style for documenting or illustrating the role of (Docker) containers in a system architecture specification?
问题描述
我打算绘制一些UML结构图，以说明Docker映像(或容器，在部署图中)在我正在构建的软件的总体结构中的位置. 我有兴趣说明容器的内容，网络端口和其他接口的映射以及多个容器的互操作方式.
I'm planning to draw some UML structure diagrams that illustrate the place of Docker images (or containers, in deployment diagrams) in the overall structure of the software I am architecting. I'm interested in illustrating the contents of containers, the mapping of network ports and other interfaces and the way multiple containers inter-operate.
我的问题空间是基于事件的分布式系统(DEBS)，所以我希望我的大多数容器都会有进出消息队列.我的体系结构的另一部分涉及内存数据网格的使用，该网格将跨越集群中多个节点上的许多容器.
My problem space is that of distributed, event-based systems (DEBS), so I expect that most of my containers will have message queues coming in and going out. Another part of my architecture involves the use of an in-memory data grid, which will span across many containers across multiple nodes in a cluster.
如何用UML建模?如果不能，那么UML中是否有计划解决此类发行问题?
How can this be modeled with UML ? If it can't, is there anything planned in UML to address such distribution issues ?
推荐答案
您要表示Docker容器及其部署数据网格的方式.但是您还想展示一下这与您的软件体系结构之间的关系.
You want to represent docker containers and how they deploy your data grids. But you also want to show how this is related to your software architecture.
我认为您应该先看看部署图.这些最适合表示跨硬件和软件环境的系统执行:
I think you should first have a look a deployment diagrams. These are best suited for representing the execution of your system across hardware and software environments:
- 这是一个示例，该示例显示了如何表示Docker主机和图像带有节点"和通讯路径
- 这是一个示例，该示例展示了如何使用工件"进一步表示节点内部例如组件，它可以表示跨多个节点链接的数据网格组件，如果是独立组件，则可以表示消息队列.
- 这是一个很好的符号概述.您的案例很有趣:您还可以显示工件在多个节点上的部署，并带有指向节点的依赖关系箭头.这将使该图专注于组件的分布方式，一方面将工件保留在另一侧，而将执行环境保留在另一侧，避免3D节点框过度膨胀.
- here an example showing how to represent docker hosts, and images with "nodes" and communication paths
- here an example showing how to further represent the inside of a node with "artifacts" such as for example components, which could represent your data-grid components linked across several nodes, and message queue if it's an independent component.
- here a nice overview of the notation. Interesting in your case: you could also show the deployment of a artifact accross several nodes with a dependency arrow to the nodes. This would make the diagram focusing on how your components are distributed, keeping artifacts on one side and execution environment on the other, avoid over-inflated 3D node boxes.
然后，如 Thomas Kilian指出的那样，可以在组件图中描述组件体系结构. 在他的评论中.为了完整起见:请参见此处或
The component architecture could then be described in a component diagram, as pointed out by Thomas Kilian in his comment. For the sake of completeness: see here or here.
Finally, you could explain the relationship between your high-level independent components and your detailed classes by using the composite structure diagram.
这篇关于是否存在用于记录或说明(Docker)容器在系统体系结构规范中的作用的公认的UML图表样式?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
