This repository has been archived by the owner on Jan 10, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 265
Defining scalable deployment nodes #38
Comments
I think having an "autoscaling" deployment node (like you see in AWS architecture diagrams) is actually a good approach. It's in the AWS DSL example too ... you could include the |
That looks good. Applied it to our architecture and it works out well. Thanks for pointing out the example. Didn't see or missed that before. It helped me to get a better understanding of how specific concepts should be reflected in the DSL. Slightly off-topic questions:
|
Thanks, you're welcome.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am currently in the process of modeling a backend system using the structurizr dsl. One part includes defining our different deployment environment which also differ in regards of scaling the services. A lot of our services are not static but instead have autoscaling implemented. However, I haven't found a good way to model this in the dsl.
Example how I modeled one of our services in a deployment environment:
Intuitively, I wanted to assign a value range, e.g. "2-10" to the last parameter of the
deploymentNode
field. However,structurizr-cli
errors telling me that parameter only accepts numbers as a value.Are there any suitable options to express the autoscaling of a service in the dsl? if not, would this be a viable feature to support?
The text was updated successfully, but these errors were encountered: