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
First, sorry if this repo is not the good place for DSL questions, I was not sure.
I know that the purpose of Structurizr is not to provide infrastructure diagram, but I was thinking about a small improvement of the infrastructureNode that can make the modelisation of the deploymentEnvironment more fluent and maybe allow a visualization from an infrastructure viewpoint.
Use case:
Let say that we want to represent a web application instance hosted in an EC2 Amazon Web Services like described in the documentation.
Current situation:
For now, we must use a deploymentNode to add the containerInstance as children, which makes a good visualization of where is running the application in the deployment view.
Problem:
Should we not consider the EC2 as an infrastructure node that host the application?
If I want to have an infrastructure oriented discussion with my team, I cannot create an infrastructure viewpoint that hide application details.
The problem is really highlighted if an infrastructure node is running multiple container instances and I need just to showcase with a simple view that e.g. the load balancer is sending requests to the EC2.
Proposal:
By allowing an infrastructureNode to have containerInstance children, it should be possible to create views that show the implied (or manually defined) relationships by hiding the container instances complexity.
Thank you
Priority
Low (I have no budget and there's no rush, please add this feature for free)
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
-
Description
Hi,
First, sorry if this repo is not the good place for DSL questions, I was not sure.
I know that the purpose of Structurizr is not to provide infrastructure diagram, but I was thinking about a small improvement of the
infrastructureNode
that can make the modelisation of thedeploymentEnvironment
more fluent and maybe allow a visualization from an infrastructure viewpoint.Use case:
Let say that we want to represent a web application instance hosted in an EC2 Amazon Web Services like described in the documentation.
Current situation:
For now, we must use a
deploymentNode
to add thecontainerInstance
as children, which makes a good visualization of where is running the application in the deployment view.Problem:
Should we not consider the EC2 as an infrastructure node that host the application?
If I want to have an infrastructure oriented discussion with my team, I cannot create an infrastructure viewpoint that hide application details.
The problem is really highlighted if an infrastructure node is running multiple container instances and I need just to showcase with a simple view that e.g. the load balancer is sending requests to the EC2.
Proposal:
By allowing an
infrastructureNode
to havecontainerInstance
children, it should be possible to create views that show the implied (or manually defined) relationships by hiding the container instances complexity.Thank you
Priority
Low (I have no budget and there's no rush, please add this feature for free)
More information
No response
Beta Was this translation helpful? Give feedback.
All reactions