onion-architecture

I'm trying to put it all together for an new architecture for existing application. Existing application has a lot of business logic, so I thought that Onion architecture (or something like that - layered, decoupled) could be the right solution - http://jeffreypalermo.com/blog/the-onion-architecture-part-1/ All examples that I have seen use Repo/UoW (on top or ORM) pattern in Infrastructure layer (or DAL, or whatever the layer that actually connects to database is called). But I'm not sure that in my case Repo/UoW (on top of EF) is necessary, because: EF6 can be nicely Unit Tested without Repo

I started to work with .net core and Entityframework 7 in Onion Architecture ! i readed this tutorial and i think its best case for learning following subject. but one part of this tutorial made a big question inside my brain. like what you see at this linked page; at Data Layer we have some classes which are our model!! public class User : BaseEntity { public string UserName { get; set; } public string Email { get; set; } public string Password { get; set; } public virtual UserProfile UserProfile { get; set; } } public class UserProfile : BaseEntity { public string FirstName { get; set; }

All entities in the domain need to have identity. By inheriting from DomainEntity , I am able to provide identity to classes. City domain entity (stripped down for easy reading): public class City : DomainEntity, IAggregateRoot { public string Name { get; private set; } public Coordinate Coordinate { get; private set; } public City(string name, decimal latitude, decimal longitude) { Name = name; SetLocation(latitude, longitude); } public City(string name, decimal latitude, decimal longitude, int id) : base(id) { Name = name; Coordinate = coordinate; SetLocation(latitude, longitude); } public

I have been reading up on the Onion architecture, and I have what I think is a simple question about how assembly dependencies should be arranged for a DI container to be able to wire everything up. Assume a very simple solution that has the following structure: UI => BL <= DAL So the UI and DAL reference the BL, but have no knowledge of each other. Also assume the BL has an interface called IDatabaseService, which is implemented in the DAL by DALDatabaseService. The container would (presumably) be configured in the UI's entry point. Since the UI has no knowledge of the DAL, how can it

Is there any difference between them (onion | hexagonal), from my understanding they are just the same, they focus upon the domain which is at the core of the application and should be technology / framework agnostic. What are the differences between them if any ? Also I see no real advantage on using one over the other or even against an N-layered architecture, if done bad just following any of them won't make any difference What are the benefits of using one over the other and why you would use it ? when to use it? Thanks choquero70 What are the differences between them if any? Onion: There