What is the difference between onion-architecture and n-layer-architecture?

Question

ASP.NET

Guys, chew pliz, what is the difference between onion-architecture and n-layer-architecture? I read about onion, they say that each subsequent top layer relies on the bottom layers, but in n-layer the top layer also relies on the bottom one, so what's the difference between them?

Answer 1

An n-layered architecture is simply an architecture built on a random number of layers. it defines the basic principles of separation of concerns and all that, but that's it.
onion - there is already a clarification that they say that in the very heart we have core-domain, entities, basic business rules. From it, the domain layer, application layer, etc. already go further. That is, first we design the core-domain and then everything else.
There is also a hexagonal one - this is again a clarification for n-layered architectures, that they say that each layer is separated from each other due to dependency inversion. Layer boundaries always have interfaces, while the outer layer always has an implementation. That is why it is called "ports and adapters architecture".