是否有一致的 UML 图样式来记录或说明(Docker)容器在系统架构规范中的作用? [英] Is there an agreed UML diagram style for documenting or illustrating the role of (Docker) containers in a system architecture specification?

查看:16
本文介绍了是否有一致的 UML 图样式来记录或说明(Docker)容器在系统架构规范中的作用?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我计划绘制一些 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:

  • 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.

这篇关于是否有一致的 UML 图样式来记录或说明(Docker)容器在系统架构规范中的作用?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆