Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

XS✔ ◾ Update Rule Styling #8821

Merged
merged 2 commits into from
Jul 3, 2024
Merged

XS✔ ◾ Update Rule Styling #8821

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9fcda08
Update rule.md
tkapa Jul 2, 2024
65e5690
Auto-fix Markdown files
github-actions[bot] Jul 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions rules/software-architecture-decision-tree/rule.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ You can find our CA template on [GitHub](https://github.com/SSWConsulting/SSW.Cl

### Vertical Slice Architecture

Vertical Slice Architecture structures your system around features rather than technical layers. Each feature is implemented end-to-end, including UI/API, business logic, and data access. This approach improves maintainability and reduces the risk of breaking changes.
Vertical Slice Architecture structures your system around features rather than technical layers. Each feature is implemented end-to-end, including UI/API, business logic, and data access. This approach improves maintainability and reduces the risk of breaking changes.

This modular approach to software development can introduce inexperienced teams to the idea of shipping features as functional units with no shared knowledge of the domain entities, infrastructure layer, or application layer within another subsystem, further preparing them for future develeopment environments that may use Modular Monolith or Microservices Architecture.

Expand Down Expand Up @@ -114,7 +114,7 @@ You have a mid-sized team, and your organization is still developing its DevOps
::: greybox
You are developing a large-scale application with multiple business domains and have several teams working in parallel.

✅ **Choice:** Microservices - Microservices allow independent development, deployment, and scaling, which suits large and complex applications.
✅ **Choice: Microservices** - Microservices allow independent development, deployment, and scaling, which suits large and complex applications.
:::

By carefully considering these factors and understanding the strengths and limitations of each architectural style, you can choose the best architecture for your system, ensuring a balance between flexibility, scalability, and maintainability.