2024-06-20 - ✨ Architecture Decision Tree - Chewing the Fat 📉 #8761
Replies: 55 comments 5 replies
-
I think it's great. I fear it may be taken as the be-all-end-all by some but as long as it's just used as a guideline, it's a great tool to
Definitely! |
Beta Was this translation helpful? Give feedback.
-
I think it's fantastic. I think this video + rule is the single most valuable piece of public IP SSW has created since I've worked here. We should absolutely send this live ASAP and promote the heck out of it. Equally, this is probably the most valuable CTF I can remember too. This is something that provides genuine value - actual, tangible, real-world guidance that developer can actually, really use in actual, real projects. We need to get this out there and do more of this sort of thing.
Understatement, I think it's invaluable. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome feedback! Thanks @matt-goldman-ssw. 🙂 |
Beta Was this translation helpful? Give feedback.
-
I think it's content is great. In its current form I find it a little hard to follow with small text and yes/no not having a consistent side but these are relatively minor points
Yes, absolutely. It could also easily be part of the spec review process |
Beta Was this translation helpful? Give feedback.
-
|
What do you think about the decision tree? It's more like a decision pyramid, but I thought it was easy to follow Do you think it would be helpful when starting a new project? Maybe... |
Beta Was this translation helpful? Give feedback.
-
|
What do you think about the decision tree? |
Beta Was this translation helpful? Give feedback.
-
|
Great video and rule! It’s easy to follow, even for someone who finds architecture talks very intimidating. 🙋🏻♀️ |
Beta Was this translation helpful? Give feedback.
-
|
Seems like this would be a great tool, invaluable for any new project. |
Beta Was this translation helpful? Give feedback.
-
It's great to help the teams making wise decisions on software architecture.
Yes, especially for new dev team. |
Beta Was this translation helpful? Give feedback.
-
|
First off, do like that we have some questions to prompt response, so +1.
I think it's great, it's clear and doesn't go too hard on every question that could be asked about every project, just some general questions to help guide you to an architecture you might not have thought of using for the project 😀
I think it'll be helpful when I am on a larger project than I have been currently getting 😅 |
Beta Was this translation helpful? Give feedback.
-
I really like this! its a super easy to follow structure that could be used by anyone.
Most definitely! |
Beta Was this translation helpful? Give feedback.
-
|
Seems logical. However these trees should be definitive and there are some subjective questions in the tree. eg. 'Do you have many teams?' Is many 2 or 7? Or 'Is the team experienced?' Is epxerienced 3 years or 10 years under belt, or is does this refer to having completed 3 or 30 similar projects? |
Beta Was this translation helpful? Give feedback.
-
|
What do you think about the decision tree? It looks simple to follow and would be a great tool to help teams with deciding on what architecture to use. Do you think it would be helpful when starting a new project? Yes. |
Beta Was this translation helpful? Give feedback.
-
|
If you follow the tree, clean architecture will now only be selected if you have an inexperienced team, and at SSW I think we never have a team without any experienced devs, at least for a serious project...so it seems like this is effectively zz-ing clean architecture - is that the desired outcome? I'd make that more explicit if so. |
Beta Was this translation helpful? Give feedback.
-
|
@calumjs - during the architecture retreat we debated a lot about CA vs VSA. My current thoughts is that although CA is great, VSA can be more productive and is easier to migrate to a Modular Monolith as the project grows as the concepts are similar (i.e. group by feature -> group by module). In comparison, converting a CA project to MoMo would be more difficult as you're using to thinking about layers, no features. |
Beta Was this translation helpful? Give feedback.
-
|
@danielmackay that's cool, and I am not necessarily against it - but the CA template was the go-to way to begin a new project at SSW since I started, so I think changing the recommendation should be made explicit with reasoning of why the recommendation has changed (rather than implicitly by just routing most circumstances away from it on the decision tree) |
Beta Was this translation helpful? Give feedback.
-
|
Although, these are my current thoughts I don't think CA is going away anytime soon. We still need to get more experience with VSA and try it out on a bunch of projects. We also need to get the VSA template to the same maturity of the CA template. |
Beta Was this translation helpful? Give feedback.
-
I think it's awesome! 😉
These sorts of things will never be perfect and cover 100% of all scenarios, but I believe it provides some good general guidance. |
Beta Was this translation helpful? Give feedback.
-
It's a quick way to get a baseline approach
Yes, is a good tool for juniors |
Beta Was this translation helpful? Give feedback.
-
Looks awesome
100% for sure! |
Beta Was this translation helpful? Give feedback.
-
Great, it can help me a lot to make a decision definitely
Yes, sure! |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Super helpful, appreciate the effort!
Yes |
Beta Was this translation helpful? Give feedback.
-
I think it's great.
Sure, it's really helpful. |
Beta Was this translation helpful? Give feedback.
-
Informative guide and easy to follow
Definitely, I will be referring to Architecture Decision Tree |
Beta Was this translation helpful? Give feedback.
-
|
Looks like a great tool |
Beta Was this translation helpful? Give feedback.
-
Yes, it would be helpful when starting the project from the beginning. Selecting the right architecture is crucial because it's the foundation of your project. If you don't choose it correctly, the project may not be sustainable in the long term. |
Beta Was this translation helpful? Give feedback.
-
|
I just realised this is the first CTF topic with a descending chart emoji rather than the regular ascending chart emoji - what does that mean 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I think this will be very helpful for teams deciding which architecture to use on a new project. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
While I dont specifically agree with the decisioning, eg uncertain requirements doesnt make for a good fit for VSA (It doesnt ake for a good fit for anything really) I think its a great starting point |
Beta Was this translation helpful? Give feedback.
-
It's a clear and well thought out guide on a complex decision. Very valuable.
Definitely. |
Beta Was this translation helpful? Give feedback.
-
|
It's a good decision tree. Though I think the best architecture is whatever gets the team off the ground the fastest in greenfields projects. One question that maybe keeps coming up - These architectures are almost always .NET focused, how can we apply them to other techs? |
Beta Was this translation helpful? Give feedback.
-
I think it is great starting point when making architectural decision on a new project.
Definitely helpful. |
Beta Was this translation helpful? Give feedback.
and others
-
Hey architects,
Rule: https://www.ssw.com.au/rules/software-architecture-decision-tree/
Beta Was this translation helpful? Give feedback.
All reactions