3 ms·
Reads like a middle part of the post... What exactly does author mean by "onion layering" and what are they being opposed to? The author supplies some examples
by theamk 2y ago
Reads like a middle part of the post... What exactly does author mean by "onion layering" and what are they being opposed to?
The author supplies some examples (new API field, new microservice dependency, new library dependency) but their fixes seem to apply to any well-organized code - I don't see why you'd need to use some mysterious "onion layering" to create a wrapper around insane dependency and isolate it from the rest of the code.
(Google searches show only a few results and they all seem slightly different, so I am guessing this variant of "onion layering" is something author made up but didn't share with anyone - their blog has only one post)
- garrettdbates 2y agoThank you for the feedback on the lack of context. Added some preamble and related background articles.
- 8note 2y agoI think you're looking for https://jeffreypalermo.com/2008/07/the-onion-architecture-part-1/ https://jeffreypalermo.com/2008/07/the-onion-architecture-pa...
- theamk 2y agoExcept your link has layers as "(Infra / UI / Tests) -> application -> domain services -> domain model", with "core" cross-cutting via inner 3 layers While OP has "config -> (API / Infra) -> core" Seems pretty different... I don't think author was referring to that particular page.
- cjohnson318 2y agoYeah, I was confused. This is basically just, "have well defined interfaces, and pass simple data through them", but with no concrete examples.