Onion, Hexagonal, Clean or Fractal Architecture? All of them, and more!
Conference (INTERMEDIATE level)
Onion, Hexagonal, Clean, or Fractal Architectures aim to organize how we deal with dependencies in our software architectures. But which one should we choose?
After distilling the essence of each approach and comparing the advantages and challenges, I’ll show how to combine all of them into an approach to use evolutionary steps towards an architecture that fits your needs from day one until the software dies.
You’ll see that layers and slices aren’t enough. A modularisation that fits the domain and simplifies understandability, changeability, and extensibility must go beyond these concepts.
After distilling the essence of each approach and comparing the advantages and challenges, I’ll show how to combine all of them into an approach to use evolutionary steps towards an architecture that fits your needs from day one until the software dies.
You’ll see that layers and slices aren’t enough. A modularisation that fits the domain and simplifies understandability, changeability, and extensibility must go beyond these concepts.
Urs Enzler
Calitime AG
Urs is a software architect and software developer with a focus on the .Net platform and Azure. He likes to build products with a short and frequent feedback loop to its users and customers - some would call this agile or continuous delivery. Besides working on the time tracking product TimeRocket, he’s a consultant on software architecture and technical aspects of working as a team using continuous delivery like evolvable design, test-driven-development and alike. He’s also the co-host of the .Net User Group Zentralschweiz. You can find his blog at www.planetgeek.ch.