Hexagonal architecture (software): Difference between revisions

Revision as of 17:32, 12 August 2019

Revision as of 17:38, 12 August 2019

Line 2:

== Origin ==

The hexagonal architecture was invented by [[Alistair Cockburn]] in an attempt to avoid known structural pitfalls in [[Object-oriented analysis and design|object oriented software design]], such as undesired dependencies between [[Layer (object-oriented design)|layers]] and contamination of [[user interface]] code with [[business logic]], and published in 2005<ref>{{Cite web|url=https://www.infoq.com/news/2014/10/exploring-hexagonal-architecture/|title=Exploring the Hexagonal Architecture|last=Stenberg|first=Jan|date=2014-10-31|website=InfoQ|archive-url=|archive-date=|dead-url=|access-date=2019-08-12}}</ref>.

The term "hexagonal" 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=":0" />.