Hexagonal architecture (software): Difference between revisions

Revision as of 15:30, 25 November 2019

Revision as of 04:09, 6 December 2019

Line 22:

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|url=https://www.worldcat.org/oclc/50292267|title=Patterns of enterprise application architecture|last=Fowler, Martin,|first=|date=2003|publisher=Addison-Wesley|year=|isbn=0-321-12742-0|___location=|pages=21|oclc=50292267}}</ref>

According to some authors, the hexagonal architecture is at the origin of the [[Microservices|microservicemicroservices]]<nowiki/>s architecture.<ref>{{Cite book|url=https://www.worldcat.org/oclc/999610958|title=Spring 5.0 microservices : build scalable microservices with Reactive Streams, Spring Boot, Docker, and Mesos|last=Rajesh R. V.|first=|publisher=Packt Publishing|year=2017|isbn=978-1-78712-051-8|edition= Second|___location=|pages=13–14|oclc=999610958}}</ref>

== Variants ==