Download as PDF, PPTX
Uploaded byThomas Pierrain
Coder sans peur du changement avec la meme pas mal hexagonal architecture
The document discusses hexagonal architecture, emphasizing its advantages such as low coupling and high cohesion in software design. It introduces concepts like ports and adapters, and highlights key principles such as deferring technology decisions and focusing on business value. Additionally, it outlines quick wins for implementing this architecture, encouraging developers to embrace changes and maintain clean, testable code.
More Related Content
Similar to Coder sans peur du changement avec la meme pas mal hexagonal architecture
Coder sans peur du changement avec la meme pas mal hexagonal architecture
- 1. @cyriux @tpierrain#MemePasMal Coder sanspeur du changement, avec la "même pas mal !" architecture hexagonale Cyrille MARTRAIRE (@cyriux) Arolla ! Thomas PIERRAIN (@tpierrain) Société Générale
- 2. @cyriux @tpierrain#MemePasMal CODER SANS PEUR DU CHANGEMENT, AVEC LA "MÊME PAS MAL !" ARCHITECTURE HEXAGONALE Cyrille MARTRAIRE (@cyriux) Arolla ! Thomas PIERRAIN (@tpierrain) Société Générale
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13. Your own SweetsBox Online! Use-cases 1. Choose your box and the sweets to put inside 2. Get a price 3. Order, & consult past orders
- 14.
- 15. As usual: Chose theDB & Design the DB schema!
- 16.
- 17.
- 18.
- 19.
- 20.
- 21. Thin layer ofUse-cases
- 22.
- 23.
- 24. Dependencies always towardsthe inside! X Allowed way for dependencies
- 25. Dependencies always towardsthe inside! Vers l’intérieur, qu’il dit le monsieur !
- 26.
- 27.
- 28. Users Vs. Providers THEY NEED ME I NEED THEM API (Application Provider Interface) SPI (Service Provider Interface)
- 29. Tests Vs. Production Delivervalue to PROD Verify behavior in TEST Test Robots Fakes, Mocks Clients Stores etc.
- 30. Scenario-Driven… Given a sweetsbox of size XL And a selection of 500g of M&Ms And assuming the following prices | item | price | currency | | XL Box | 2.50 | EUR | | M&M (100g)| 5.00 | EUR | ! When I ask for a price Then the price is 27.50 EUR
- 31. Modeling the domain… Sweets CustomSweetsBox SweetsBoxPricer AllOrders CatalogOrder ShippingCostEstimat or Caramels Nougat Fudge
- 32. Modeling the domain… Sweets CustomSweetsBox SweetsBoxPricer AllOrders CatalogOrder ShippingCostEstimat or Caramels Nougat Fudge Beware of Modelism!
- 33. I need tocall external services, but I don’t want to know about them
- 34.
- 35.
- 36.
- 37.
- 38.
- 39. Add an htmlweb app… “REST” Adapter
- 40.
- 41. Quick Win 1 Focuson what really matters
- 42.
- 43. Implement the repository Onthe cloudz!
- 44.
- 45. Même pas mal! (“that didn't hurt one bit“)
- 46. Quick Win 2 Choosethe technology last (when we know best)
- 47.
- 48. 48 Who’s that architect who can’t decide the technologies early?
- 49. Ebay as additionalretailer?
- 50. Ebay as additionalretailer! “REST” Adapter Ebay Adapter
- 51.
- 52.
- 53.
- 54.
- 55. Quick Win 3 Embracethe changes
- 56. X Allowed way for dependencies Hexagonalarchitecture
- 57. Quick Win 4 Lowcoupling High cohesion
- 58.
- 59.
- 60. Quick Win 5 Ourbusiness code is not victim of IT fads anymore!
- 61.
- 62.
- 63. Need other areasof behaviors? • Business intelligence? • Supply Chain management • CRM? • …
- 64. Même pas ! ;-)
- 65. Hexagonal all thethings New Bounded Contexts? New Micro-services?
- 66. Main benefits ! 1.Focus onwhat really matters (business value first!) ➔ have you ever tried DDD? ! 2.Choose the technology last (when we know best our concrete needs) ! 3.Embrace the changes (“Même pas mal !” / “that didn't hurt one bit“)
- 68. Thanks! Cyrille MARTRAIRE @cyriux ThomasPIERRAIN @tpierrain
- 69. @cyriux @tpierrain#MemePasMal CODER SANS PEUR DU CHANGEMENT, AVEC LA "MÊME PAS MAL !" ARCHITECTURE HEXAGONALE Cyrille MARTRAIRE (@cyriux) Arolla ! Thomas PIERRAIN (@tpierrain) Société Générale
- 70.
- 71.
- 72.
- 73.
- 74.
- 75.
- 77. Port = ExistingTechno Adapter = Your code
- 78.
- 79.
- 80.
- 81.
- 82.
- 83.
- 84.
- 85.
- 86. Steeve Freeman &Nat Pryce (GOOS) 86
- 87.
- 88. Jeffrey Palermo (OnionArchitecture) 88
- 89.
- 90.
- 91.
- 92. +--------------+! | presentation |! |--------------|! |domain |! |--------------|! | persistence |! +--------------+ Layers?
- 93. +-----+-------------+----------+! | gui |file system | database |! |-----+-------------+----------+! | domain |! |------------------------------+ Infra the other way round! Layering http://matteo.vaccari.name/blog/archives/154
- 94.
- 95.
- 96. Un Dedans et Un Dehors #desreperes pour nos enfants
- 97.
- 98.
- 99.
- 100.
- 101. Sentiment Analysis ! Automatically extractthe sentiment of English sentences submitted on the web, using a given lexicon. Keep track of the submitted sentences.
- 102. Your Turn ! 5mn Small groups Anytechnology / approach Propose an architecture on paper ! Then we’ll debrief a selection of them
- 103. Sentiment Analysis ! Automatically extractthe sentiment of English sentences submitted on the web, using a given lexicon. Keep track of the submitted sentences.
- 105.
- 106.
- 108.
- 109.
- 110.
- 111.
- 112. 4 novel coupling metrics 1. Undesirable Dependency Count 2. Undesirable Distinct Dependency Count 3. Undesirable Dependency Max Repetition 4. Undesirable Distinct Assembly Count ! Bad Good ● Provoke conversations
- 113.
- 114.
- 115.
- 116. Hexadecimal Architecture: Need at least 16layers in the code
- 117.
- 118. Architecture ! ”The key technologychoices” BOF…
- 119.
- 120.
- 121.
- 122. Reversible decisions FTW! Defer technology decisions Changeyour mind easily
- 123.
- 124. 50% TECH 50% COMM (10%MATHS)
- 125.
- 126.
- 127. ”Le principe dunombril : on regarde vers l’intérieur”
- 128.
- 129. Persistence Ignorance ! ! •You can defer decisions about persistence (and UI) for a long ^me •Your domain must NOT care!
- 130. Un service, la facade coté mé^er d’un stockage ! Sans jamais parler de base de données. Repository h;p://www.andeka.co.cc/2011/07/postbox-‐251.html
- 131.
- 132.
- 133.
- 134. Bubble Context • Createa little bubble of innovation ! • Brand new model ! • As clean as we like • Highly tested • High hygiene standards
- 135. Bubble Context • ACLto protect from the legacy code ! • Translates legacy objects & services into new, cleaner ones
- 136.
- 137. Module (lib) <<ValueObject<<ValueObject <<ValueObject>> <<ValueObject <<ValueObject>> <<Service>> <<SPI>> <<Service>> <<API>> <<En7ty>> <<Aggregate>> Module == library Accès aux services extérieurs
- 138. Module == library Accès aux services extérieurs
- 139. Hexagonal Architecture Scenario test data Adapters
- 140.
- 141. Bounded Contexts Il n’est pas possible de convenir du sens précis des mots u7lisés par un grand nombre de personnes. ! Il faut accepter ce fait, et donc définir dans quel contexte un langage est clairement défini sans ambiguité.
- 142. Different MY activity isnot the
- 146.
- 147. Wrap-up • Concepts &Messages – Subir -> Délibéré – Intérieur Vs Extérieur – Gérer ses dépendances – Langage interne / externe – DIP • Exemples • Kata
- 148. Content • When notto go Hexagonal? – Conformist – Facebook game – Too small (connector…) ! • Advanced aspects – The adapter pattern – Tech ports diversity – 1 Adapter – many interfaces – 1 interface – many adapters – Data push – Session management – Adapter as a module indeed
- 149. Content 2 Domain modelas a Pure Functions (100% no Entity inside) vs as Aggregates ! -- The Repository pattern Reuse slides Hexagonal for a Bubble Context within a legacy ! Ports = surrounding legacy Adapters = repository / adapter ! Cloakroom / clandestine passenger patterns
- 150. Content 3 How toenforce? ! Discipline Maven multi modules, .Net projects Static analysis: JDepend rules, NDepend, Sonar plugins — Bounded Context Reuse slides ! Conformist vs ACL isolation Same language or not? ! Autonomous Components / Polyglot persistence ! Influence of sync vs async / push vs pull on the inside of the hexagon ! Examples? Living Documentation Convention (YES)? Annotation on packages? ! The Bounded Contexts / the Domain models vs the rest (ici un seul Bounded Context) ! Domain model -> inside Everything else - that implements something from the domain model -> at the right - everything else that only calls - > at the left !
- 153.
- 154.
- 155. http://matteo.vaccari.name/blog/archives/154 Problem: write a program that 1. Loads a set of employee records from a flat file 2. Sends a greetings email to all employees whose birthday is today ! The flat file is a sequence of records, separated by newlines; this are the first few lines: last_name, first_name, date_of_birth, email ! Doe, John, 1982/10/08, john.doe@foobar.com ! Ann, Mary, 1975/09/11, mary.ann@foobar.com ! The greetings email contains the following text: Subject: Happy birthday! Happy birthday, dear John! with the first name of the employee substituted for “John” ! 3. REST service to query past greetings ! HINT: today is a tech port! ! ! +-----+-------------+----------+! | gui | file system | database |! |-----+-------------+----------+! | domain |! |------------------------------+ +--------------+! | presentation |! |--------------|! | domain |! |--------------|! | persistence |! +--------------+ Exercise Postgres Sql + Gui (+ myBatis ?) Audit et log dans le domain + Metrics