Onion Architecture in ASP.NET Core

preview_player
Показать описание

In this video, we are going to learn about Onion architecture and what are its advantages.
We will show a RESTful API project that follows the Onion architecture, with ASP.NET Core. After the initial explanation and the project presentation, we will talk about the advantages of this architecture and why should you use it, so try to stick to the end of the video.

LINKS MENTIONED IN THE VIDEO

FOLLOW US ON SOCIAL MEDIA!
Рекомендации по теме
Комментарии
Автор

Thank you all for watching and for your support.

CodeMaze
Автор

Excellent, very clear and valuable.
Thank you very much.

talkathiriify
Автор

Hello, thank you very much, this is very interesting, can I download the example somewhere?

camiloramos
Автор

I really like it :)
I just have one question, what do you think about Result pattern instead of exception handling for domain issues?

NikolaGolijanin-ms
Автор

Thank you very much, it helped me a lot :D

awadelatam
Автор

I have read your book and I have a question? Do we need to register all the repository to the DI or just the RepositoryManager ?

Sayada
Автор

Hello, thank you very much for this video. I am currently developing an API and have a couple of questions related to onion architecture. Would really appreciate if you could answer them. Thanks anyway.

1) I wonder if i should return something in add, remove, update methods in Services and Repositories. Currently I am just returning added, modified or deleted object. Is that okay?

2) According to the video we should place an email related services, or services which connect to third-party apis to Persistence layer. But where should we put interfaces that they are derived from? And should we derive them from any interfaces?

AhmadAhmadzada-uv
Автор

Is the repository design pattern necessary with the use of the Entity Framework?

ChosenThings
Автор

Hi,
I am still confused about how the initial migration from the Infrastructure layer can know the database connection string from the API layer. Isn't it the API layer that calls the Infrastructure layer as a reference and not the other way around?

kristiadhy
Автор

What is the difference between clean and onion because the way they split the layer is really the same, the only difference is that one layer is called Application, one is Service ?

Sayada
Автор

This pattern makes me hate programming for some reason. I guess I had a bad initial experience with it.

michaelderobio