Hexagonal Architecture

[@ruixue6955]

0:40 motivation 1:34 the Hexagon 1:51 the *6 sides represents the 6 different ways of communicating with the system* 2:36 it is a perfect fit for domain driven design 3:12 the outside 3:24 like *REST, http, binary, SOAP, SQL* etc. or *other Hexagonal system* 4:20 framework layer - 4:40 this is the place that transfers the incoming stream to an object that we can work on 4:45 in the case http e.g. 5:08 example in Java 6:15 what a command bus is => application 6:42 application layer is: 7:00 a man in the middle 7:08 code demo of command bus - the CB class 8:46 domain layer 9:58 ports & adapters - 10:14 adapters are fitting into those ports 10:18 ports are like the sides on the hexagon 10:32 adapters are like each layer in the 10:49 an *adapter is the implementation, a port is an interface* 11:21 use case 11:27 a command is represented as a use case 11:41 good thing: you implement your command/use case once, then you are totally agnostic of the technical implementation 11:53 one team can focus and can design on the use case without the system being actually fminished 12:01 while another can already starts implementing the ports that are coming into the system independent of a specific use case 12:18 *boundaries* in the Hexagon 12:33 each layer protected itself with a boundary from the outer layer 13:16 so the *dependencies are coming from outside in* 13:21 the domain is independent from the *application* , application is independent from the *framework* 13:33 how to achieve that: *inversion of control* / *dependency injection* 14:07 problem with using xml in Spring: 14:13 your system is not independent, beans set up in the XML are not independent from each other, at least they are dependent from the framework 14:35 in *Spring* 4, it is possible to set up *context classes*

[@impostersyndromedev]

An excellent summary of Martin's book, Clean Architecture. I'll be sharing this!

[@GregSaturn]

This is great! Thanks for sharing - Would you consider putting the links from the slide into the description? It would make it a lot easier for the audience.

[@MarcusBiel]

This talk actually based on a talk from Chris Fidao, a PHP developer, and also influenced a bit by a talk from Robert C Martin. Hexagonal architecture maintainabilityFirst of all let’s talk about the motivation for the hexagonal architecture. Hexagonal architectureWe try to improve the maintainability with hexagonal architecture because it is very important that we can do easy changes and that we can change this software very fast. The faster we can make changes, of course the less time it needs us and so or system can be developed faster and cheaper. The more the technical dept increases the lower is our maintainability and hexagonal architecture want’s to improve that with the use of layers, just as well as many other architectures. Okay so now let’s have a look. Here we see the hexagon. The hexagonal architecture, as you might guess is called hexagonal architecture because of this image here, the hexagon...

[@damodarmaddina]

Thank you, great job

[@ruixue6955]

15:07 in hexagonal architecture, we do need *interfaces* 15:21 each layer is independent of the next one 15:47 from Robert C. Martin:

Thank you for this introduction.

[@MarcusBiel]

You're welcome! :)

[@JanacMeena]

Thanks for this.

[@Fataho]

thanks

[@fernandofranzini8219]

To Brazilian friends on the subject - - www.udemy.com/course/arquitetura-hexagonal-com-java-1/

[@alirezaRahmanikhalili]

good job

[@MarcusBiel]

thanks :)

[@dannyho5532]

Your explanation is over simplified. Also your articulation is poor.