Comments on: Onion Architecture?

By: steinjak

steinjak — Mon, 20 Oct 2008 06:59:46 +0000

I just felt that somebody ought to mention Cockburn's Hexagonal Architecture here, which I feel is somewhat related to this. When trying to structure an architecture according to those principles, we ended up doing basically the same thing as in the "Onion architecture".

By: So you want to learn NHibernate - Part 0.5, Prerequisites (or NHibernate = Marijuana.NET) | The Freak Parade

Fri, 08 Aug 2008 22:39:46 +0000

[...] Onion Architecture Part 1, Part 2 and Part3 The name, perhaps, is rather silly, but Jeffrey Palermo does a very nice job of describing how an ideal DDD architecture should be [...]

By: Davy Brion

Davy Brion — Wed, 30 Jul 2008 18:30:16 +0000

i dunno… you’re right, but it has a bit of an academic ring to it…

By: Jan Van Ryswyck

Jan Van Ryswyck — Wed, 30 Jul 2008 18:20:29 +0000

The book “The Pragmatic Programmer” talks about an orthogonal architecture, and this is just derived from plain old OO design reinforced by Eric Evans DDD. Onions kinda smell and make you cry if you want to peal them, so maybe “orthogonal architecture” fits the bill?

By: Davy Brion

Davy Brion — Wed, 30 Jul 2008 16:02:48 +0000

ah ok… i thought you were talking about Domain Specific Languages

i do agree that the Onion architecture is a way of doing Domain Driven Design, and that there are certainly other ways of doing so.

By: Gonzalo

Gonzalo — Wed, 30 Jul 2008 15:58:16 +0000

Basically when you create your apps to solve a specific problem. This will make your design base on a specific “Domain Model” and creates “Domain Services” the DB or storage source become “external”

By: Davy Brion

Davy Brion — Wed, 30 Jul 2008 15:00:13 +0000

@Gonzalo:

what exactly do you consider a DSL design?

By: Gonzalo

Gonzalo — Wed, 30 Jul 2008 14:57:28 +0000

I feel the “Onion Architecture” is just one way of using a DSL design. Any comments?

By: Davy Brion

Davy Brion — Wed, 30 Jul 2008 06:53:59 +0000

heh… or Onion Driven Development specialists

By: Nathan

Nathan — Tue, 29 Jul 2008 22:21:53 +0000

Ha! I completely agree. Wonderful architectural description, awful name. Reading the header of the post you assume you’re about to read a description of how NOT to design a system, and are quite surprised to learn it is the opposite. Plus, onions don’t have a core, just layers. Peel the last layer and your hands are empty. Even so, it’s hard to come up with a better name.It is hard to imagine the name catching on. I can’t really picture reading resumes with “Experience building onion based systems” or “Solid understanding of onion architecture”