Hexagonal architecture (software): Difference between revisions

Revision as of 12:58, 10 October 2022

Revision as of 12:16, 15 January 2023

Line 22:

== Criticism ==

The term "hexagonal" implies that there are 6 parts to the concept, whereas there are only 4 key areas. The term’s usage comes from the graphical conventions that shows the application component like a [[Hexagon|hexagonal]] cell. The purpose was not to suggest that there would be six borders/ports, but to leave enough space to represent the different interfaces needed between the component and the external world.<ref name=":020">{{Cite web|last=Cockburn|first=Alistair|date=2005-04-01|title=Hexagonal architecture|url=https://alistair.cockburn.us/hexagonal-architecture/|access-date=2020-11-18|website=alistair.cockburn.us}}</ref>

According to [[Martin Fowler (software engineer)|Martin Fowler]], the hexagonal architecture has the benefit of using similarities between presentation layer and data source layer to create symmetric components made of a core surrounded by interfaces, but with the drawback of hiding the inherent asymmetry between a service provider and a service consumer that would better be represented as layers.<ref>{{Cite book|title=Patterns of enterprise application architecture|last=Fowler, Martin|date=2003|publisher=Addison-Wesley|isbn=0-321-12742-0|pages=21|oclc=50292267}}</ref>