u/sttingin r/softwarearchitecture • Recommends
On “The Deception of Onion and Hexagonal Architectures?”
I think it is a nice video for you OP 😊 link to this video
0:00 / 0:00
#hexagonalarchitecture#portsandadapters#alistaircockburn
Hexagonal Architecture (Alistair Cockburn)
Tech Excellence
6.1K subscribers • 2 videos on Hallway
- Recommended by 2 people: 1 on Lobsters and 1 in engineering communities.
- Presented by Alistair Cockburn, co-author of the Agile Manifesto
Intermediate. Assumes working knowledge.
32K views1 year ago2 recommendations
Software designSoftware architectureDesign patterns
Alistair Cockburn explains the rules, structure, history, and benefits of the Ports and Adapters architecture, also known as Hexagonal Architecture.
Learn from it’s creator the rules and structure of the “Hexagonal”, more correctly called the Ports & Adapters architecture. In this lecture, Dr. Cockburn will describe why he created it, its benefits and also its costs, the UML description, and also some sample code. As an extra challenge, he will invite you to write your first Ports & Adapters application in your favorite language /during/ the talk! Outline of the lecture: - Challenge to write a small application during the lecture - Short form what the code looks like - Costs, benefits, history: why was it needed - Viewing your application as a component - Development sequence - Examples in Ruby & Java with needed terminology - How to set up the folders - The various ways to set up the architecture - Why is it called /Hexagonal/? - Summary, checking in with people who accepted the challenge ABOUT ALISTAIR Dr. Alistair Cockburn (pronounced CO-BURN) was named as one of the “42 Greatest Software Professionals of All Times" in 2020, as a world expert on methodologies, project management, software architecture, use cases and agile development. He co-authored both the Agile Manifesto in 1002. Since 2015 he has been working on expanding agile to cover every kind of initiative, including social impact projects, governments, and families. Dr. Cockburn developed the “Hexagonal” or Ports & Architecture over several decades out of frustration seeing projects suffer from not being able to swap drivers and databases easily. For his latest work, see alistaircockburn.com/. - LinkedIn: linkedin.com/in/alistaircockburn/ - Twitter: x.com/totheralistair - GitHub: github.com/totheralistair - Personal site: alistaircockburn.com/ TECH EXCELLENCE - Subscribe to our YouTube channel youtube.com/@TechExcellence - Join our Meetup Group meetup.com/techexcellence - Follow us on LinkedIn linkedin.com/company/techexcellenceio - Follow us on Twitter twitter.com/techexcellence_ - Join our Discord Community discord.gg/KXdf4t4j2m #hexagonalarchitecture #softwareengineering #techexcellenceWhy it's here
2 people recommend thisWhat people say. Recommended as an excellent explanation of hexagonal architecture directly from its creator.
u/kxc42in r/scala • Mentions
On “hexagonal/clean architecture with DDD in scala”
I think you are a little bit out of luck. I've been in software & scala development for quite some time and I did not see any example that I would call "good enough". I think there some factors that lead to the absence of examples:
* there is a huge chunk of interpretation and personal preference in (hexagonal) achitecture. It already starts with how to name packages and how to organise your project.
* if you work with microservices, the services are often small enough so that you can use much simpler architectures with less overhead
* usually you have one or two devs that are fans of hex arch, but there is no buy-in from the company and other teams/team members. This leads to an even bigge…