"Architecture is really important. The things that are hard to change are the initial architecture, the culture, and the skills of the team. That's why it's important to get it right from the start." -Martin Fowler

After a period of stammering where we coded as best we could, we believed, after the 2000s, to have found the ideal architecture: a division into sofas, where each would have a dedicated responsibility.

Years later, a whole host of problems have surfaced when maintaining and scaling the software, especially with the abundance and lifecycle of frameworks.

In order to overcome these problems, architectures have emerged, including the Hexagonal architecture and the Clean architecture.

But what do they really bring?
Is it just marketing or real added value?
Are they equivalent with different naming?
Finally... are they the only answer to all problems?

All the answers will be given in this talk, as well as the advice that Alistair Cockburn gave me when we met

The talk is divided into 4 parts:
- history of application design (DB driven design, big ball of mud architectures, layered architectures, etc.)
- arrival of hexagonal architecture and description (why, strength, weakness, etc.)
- description of the Clean architecture and comparison with the hexagonal architecture
- journalist interview: hexagonal or clean? And arguments.

Talk given in several forms in many conferences, on stage (Paris, Rennes in France, Mons in Belgium, Prague in czech republic, etc.) or remote.
Other dates are planned.
The talk is very appreciated by the participants :
- https://twitter.com/Horgix/status/1674021086059712513
- https://twitter.com/Horgix/status/1674025063660544000
- https://twitter.com/slecache/status/1674018345635463171

Replay available in english here : https://youtu.be/er3tXxhyONY?feature=shared