421
General Board / Re: Deployment Diagram questions
« on: June 22, 2018, 07:55:54 pm »
"We've been simply using a single node using a naming convention 'Cluster'<Type><RootName><Node1Name>/<Node2Name>/etc. So example ClusterAIXFluffA/B/C. However, there are times when we'd like to specify differences in node behavior in instances of the same cluster type. So ClusterAIXFluffA/B/C is a mirrored redundant set of nodes but ClusterAIXPeanutA/B/C has a primary node with two fail-over nodes. Our engineers need to know that a node failure on ClusterFluff is automatically handled and no special code needs to be written."
In my opinion the problem is that this is not information that should described in a deployment diagram. There are other diagrams where you can describe classifier properties, behavior and interaction logic.
In my opinion the problem is that this is not information that should described in a deployment diagram. There are other diagrams where you can describe classifier properties, behavior and interaction logic.
