#hexagonalarchitecture#onionarchitecture#cleanarchitecture
172K subscribers • 49 videos on Hallway • Conference channel
Intermediate. Assumes working knowledge.
10K views1 year ago
Software designSoftware architectureDomain-driven designSimplicity and complexity
Oli critiques domain-centric architectures like Hexagonal and Onion, discussing their complexity and trade-offs in real-world software projects.
To separate technical from domain code, architectural approaches like Hexagonal or Onion Architecture are currently all the rage. However, discussions about their semantic details and their mapping to the source code structure of software projects are at least equally ubiquitous.How much abstraction and mapping between architectural concepts is needed? Is persistence metadata in the domain model heresy? Above all: what is the actual goal of the exercise, and: does it have to be so complicated?We address these and other questions in a theoretical overview and by looking at concrete examples. We discuss the trade-offs of different approaches and how various tools and libraries help us to maintain the intended structural integrity.Devoxx is on Hallway's list of conference and university channels, and this upload is one of its most-watched talks or lectures. Nobody has recommended it in the communities yet, so it ranks below community picks.
u/olivergierkein r/softwarearchitecture • Mentions
On “A well-structured layered architecture is already almost hexagonal. I'll prove it with code.”
u/olivergierkein r/softwarearchitecture • Mentions
On “The Deception of Onion and Hexagonal Architectures?”
u/olivergierkein r/softwarearchitecture • Mentions
On “How doe modules interact each other in Hexagonal Architecture?”
u/olivergierkein r/softwarearchitecture • Mentions
On “Modularity vs Hexagonal Architecute”
u/olivergierkein r/softwarearchitecture • Mentions
On “Is hexagonal architecture good design or just extra layers with better branding? [Manning Giveaway]”