Last post Jul 22, 2014 02:26 AM by BetsyASP
Jul 20, 2014 08:06 PM|Alex_808|LINK
I am looking to understand and implement the Onion Architecture. After reading a few articles and looking at examples I have a vague idea on how to structure everything but need help to clear up some of my confusion.
Based on different examples and articles I Have read I created the above structure. One of my main confusion comes when I look at "02-Service: Services Interfaces". Lets take the IUserService.cs. I assume this interface would contain different signatures like
RegisterUser(), LoginUser(), BanUser(), ModifyUser(), ChangeAuthenticationLevel() and so on? Is this correct? If not what other examples would we find? And are these considered Domain Services or Application Services?
Jul 22, 2014 02:26 AM|BetsyASP|LINK
Please refer the following kb article:
Onion Architecture is a specific type of solution architecture that was first introduced to me by Jeffrey Palermo. Over the years nearly every project I’ve worked on used a traditional layered architecture under the guise of loose coupling. Yet in every
case as the project progressed we realized more and more that our layer abstractions weren’t actually abstractions at all. We were still building our application on top of a specific technology, which is sure to change over time. Additionally, when we needed
to add a new feature to the UI, the developer is completely free to put the code for his feature in any layer he chooses — from the presentation layer on down, or perhaps in the dreaded “Shared/common/utility” project.