Domain Driven Design - Onion Architecture in 2 Minutes

preview_player
Показать описание
For more on Domain Driven Design enrol to my course at 80% OFF ($9.99)

Onion architecture is a pattern that is often adopted during DDD since it separates different architecture layers.

The complexity of the domain is protected in its own layer that acts as the core.

It emphasises the decoupling of the UI with the business logic layer - YES there are still dependencies for the UI to behave as expected - however coupling these two makes it harder for the system to integrate with change... And This is what we are trying to prevent.
Рекомендации по теме
Комментарии
Автор

I don't think that Adapters are into the Application Services Layer, which itself belongs to the Application Core.
I think the Adapters layer is a layer around Application Services, that is to say : between the Application Services and the Infrastructure layer.
Because if we change anything into the Infrastructure, we also have to change some Adapters, and we DON'T want to have to modify the Application Services in a such case. Application Services layer is about use cases, not depending on how Adapters / Infrastructure evolve.

LinkingWorlds
Автор

I am the almighty onion bot and I approve this message

onionbot
Автор

Why do you think, that DDD - it's about Onion architecture? Maybe DDD - it's language for speaking with our business?

goose
welcome to shbcf.ru