No, it is not a great video, he struggle too much explaining the basics, at this moment I wonder if he even knows why this architecture is used, it seems he mechanically follows up another tutorial
This another flavour of traditional n layered architecture . If its an onion architecutee the inner most slice is dataaccess and nothing but a poco without any business domain related logic . the data flow is ui -> service -> repository ( dataaccess as a contract ) isnt it a traditional layered architecture ?
I would like to ask , is the IRepository is sharing repository for all services ? why we need separate it as 2 project? any one can help me answer thanks
Nice try, this is not onion arch itself, it is simple and plain N-Ties arch. The onion architecture is a software design pattern where the code is structured into layers, akin to the layers of an onion. The innermost layer represents the core business logic and data, surrounded by layers for application services, use cases, interfaces, and infrastructure. Each layer only depends on the layer directly beneath it, promoting separation of concerns and making the code more maintainable and testable. The outermost layer acts as a protective boundary, ensuring the inner layers remain secure and isolated from external influences (to keep it stable).
This is simple Layer architecture not onion architecture. Repository layer is added for separation between Data access layer and service layer.
Can you please suggest better video for this architecture
@@sanjayrorua-cam.com/video/QkJUd8C7-_I/v-deo.html
This is not a Onion Arch itself
No, it is not a great video, he struggle too much explaining the basics, at this moment I wonder if he even knows why this architecture is used, it seems he mechanically follows up another tutorial
Messed it up isnt it ? data-access layer holding only entity objects, Direct reference from UI to DAL. I dunno what i just watched but this is wrong
This another flavour of traditional n layered architecture . If its an onion architecutee the inner most slice is dataaccess and nothing but a poco without any business domain related logic . the data flow is ui -> service -> repository ( dataaccess as a contract ) isnt it a traditional layered architecture ?
Can you please suggest better video for this architecture
this is not an onion architecture.. your repository has direct dependency with ui project..you must need to know about onion architecture..
Can you please suggest better video for this architecture
Thanks. Great video. Do you have the source code that I can download?
I would like to ask , is the IRepository is sharing repository for all services ? why we need separate it as 2 project? any one can help me answer thanks
This is not Onion architecture, it's N-¬Tier.
Where is Uow pattern
Nice try, this is not onion arch itself, it is simple and plain N-Ties arch. The onion architecture is a software design pattern where the code is structured into layers, akin to the layers of an onion. The innermost layer represents the core business logic and data, surrounded by layers for application services, use cases, interfaces, and infrastructure. Each layer only depends on the layer directly beneath it, promoting separation of concerns and making the code more maintainable and testable. The outermost layer acts as a protective boundary, ensuring the inner layers remain secure and isolated from external influences (to keep it stable).
Couldn't understand what he is saying
Can you translate
Translate to what......english! 😃
Haters gonna hate. BTW nice vid
Not correct