Does onion architecture include SOLID principles?

Question

0.00/5 (No votes)

See more:

I am reading and learning on how an application project could be designed better by following the SOLID and CRAP principles. I am quite comfortable in understanding the CRAP principles. However, while researching, I came across the concept of Onion architecture and I am having difficulty wrapping my head around the 2 design concepts and the differences/similarities between the two, if any?

Will an Onion architectured project include the SOLID principle(s)? Does one approach correlate to the other?

What I have tried:

If someone can briefly explain the relation between the two concepts it would be really helpful. Thank you.

Posted 7-May-17 16:52pm

Truecolors

Updated 8-May-17 2:18am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CHill60 · Accepted Answer · 2017-05-08T02:18:00

If anything I believe Onion helps enforce the "S" (Single Responsibility), and because of the interfaces or contracts between the layers it strongly supports both the "L" (Liskov substitution) and the "I" (Interface segregation).
Like most environments, frameworks and theories the "O" (Open/closed) and "D" principles are down to the designer

You may find the following blogs useful:
The Onion Architecture. The software architecture to the rescue of the SOLID principles[^]
The Clean Architecture | 8th Light[^]