/explore
|
You are here 
|
www.bennadel.com | ||
| | | | |
herbertograca.com
|
|
| | | | | Documenting Software Architecture When we need to explain to someone else (new developer, product owner, investor, ...) how the application works, we need documentation. But what documentation options do we have that can express the whole application building blocks and how it works?! In this post I'm going to write about: - UML - 4+1... | |
| | | | |
www.jamesmichaelhickey.com
|
|
| | | | | How should you design the structure of your .NET solutions? Microservices? Monolith? Feature folders? Clean architecture? Shared databases? | |
| | | | |
martinfowler.com
|
|
| | | | | Software Architecture is the important aspects of a software system's internal design, usually its major components and aspects that are hard to change. | |
| | | | |
www.softdevtube.com
|
|
| | | The onion architecture is not as well known as the 3-tier software architecture but is gaining a lot of attention during the microservices era. It structures your software so that it is easy to change technologies without impacting business logic. Coupled with Domain Driven Design (DDD) principles it offers a powerful way to build a | ||
