You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When modeling a rather big and complex Software System, I often found that I model in my head a relationship between element A and element B as "going through" element C. This comes natural when I have to model services like API gateways or reverse proxies: e.g. I want to model the fact that a GUI (deployed in a browser) is in relationship with a back-end service (deployed on server X), but in some cases it is also important to communicate that the relationship "passes through" a reverse proxy that may be deployed on server Y.
I know that I can model this creating a relationship A -> C and another C -> B, but this quickly becomes cumbersome as C is typically used as gateway for a lot of different communications, and the original relationship A -> B (which is the actual "semantic" relationship) gets lost.
Are there plans to support this kind of "going through" relationship feature?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When modeling a rather big and complex Software System, I often found that I model in my head a relationship between element A and element B as "going through" element C. This comes natural when I have to model services like API gateways or reverse proxies: e.g. I want to model the fact that a GUI (deployed in a browser) is in relationship with a back-end service (deployed on server X), but in some cases it is also important to communicate that the relationship "passes through" a reverse proxy that may be deployed on server Y.
I know that I can model this creating a relationship A -> C and another C -> B, but this quickly becomes cumbersome as C is typically used as gateway for a lot of different communications, and the original relationship A -> B (which is the actual "semantic" relationship) gets lost.
Are there plans to support this kind of "going through" relationship feature?
Beta Was this translation helpful? Give feedback.
All reactions