Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Conscious Coupling

426 vues

Publié le

By using a comprehensive feature-filled framework we can build software fast. On the other hand, by decoupling our applications we can build sofware that is independent of our framework and infrastructure choices, and therefore longer lasting.

We can't do both, is one approach always right?

In this talk we'll look at different decoupling techniques, what problems they solve, and when they make sense. We will learn some concrete techniques to discover where we should be investing in decoupling, and when we should let the framework maintainers do the work for us.

Publié dans : Logiciels
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Conscious Coupling

  1. 1. Conscious Coupling Building Software that Lasts Ciaran McNulty at SymfonyLive London
  2. 2. Me Hi, I'm Ciaran and I'm a PHP developer I am a consultant with Inviqa I maintain PhpSpec
  3. 3. My early period: Follow the framework!
  4. 4. SymfonyLive London 2013 Konstantin Kudryashov and Marcello Duarte - The Framework as an Implementation Detail
  5. 5. SymfonyLive London 2014 Matthias Noback - The Naked Bundle
  6. 6. My middle period: Decouple all the things!
  7. 7. Modelling by Example Konstantin Kudryashov (again)
  8. 8. My current period: Couple some of the things!
  9. 9. What is coupling?
  10. 10. class TaxiDispatcher { function dispatch (Car $car, $destination) { $this->chargeCustomer(); $car->goTo($destination); } }
  11. 11. Problems with dependencies —Changes to Car mean changes to Dispatcher —Can't reuse Dispatcher with new vehicles
  12. 12. interface Vehicle { public function goTo($destination); } class TaxiDispatcher { function dispatch (Vehicle $vehicle, $destination) { $this->chargeCustomer(); $vehicle->goTo($destination); } }
  13. 13. Benefits of abstraction —Now we only need to rewrite Dispatcher and Car when Vehicle changes —Vehicle can be very stable; it's just an interface —Can make new transportation types that implement Vehicle
  14. 14. Defining abstractions —Start with the use case, not the implementation detail —Contract should be a simple as possible —Contract should focus on responsibilities —Hide details of underlying APIs
  15. 15. Example - upgrade eligibility Bad abstraction: interface HttpClient { public function getData : array ($url, $parameters); }
  16. 16. Example - upgrade eligibility Better abstraction: interface UpgradeEligibilityChecker { public function getContractId : int ($phoneNumber); public function isEligibleForUpgrade : bool ($contractId); }
  17. 17. Example - upgrade eligibility Best abstraction: interface UpgradeEligibilityChecker { public function isEligibleForUpgrade : bool ($phoneNumber); }
  18. 18. Abstraction via interfaces —You still need to know what methods to call —Caller has to respond to changes in the callee
  19. 19. Taking it further: Events and Commands
  20. 20. —Migrate actions from method calls to objects —Depend on a bus rather than depending on contracts —Don't know anything about what handles the action
  21. 21. Events Direct coupling: $notifier->notifyLawyersAboutPurchase($id, $item, $cost); Event style (symfony/event-dispatcher): $eventDispatcher->dispatch( 'item.purchased', new ItemWasPurchased($id, $item, $cost); );
  22. 22. Commands Use case / service style: $invoiceApprover->approveInvoice(1234); Command style (thephpleague/tactician): $commandBus->handle( new ApproveInvoice(1234); );
  23. 23. Advantages of decoupling via abstractions —Cleaner APIs —Swappable components —Separation of concerns —Easier to test —No 'ripple effect' around changes
  24. 24. Disadvantages of decoupling via abstractions —Makes execution flow harder to follow —Adds more complexity (more files in codebase) —Cognitive cost of thinking of good abstractions
  25. 25. Decoupling from infrastructure
  26. 26. —Abstractions are going to change when the use cases change —Interfaces are more tightly coupled to code that uses them —Interfaces 'belong' in the same architectural boundary as the code that uses them.
  27. 27. Frameworks Coupling to other people's code
  28. 28. Highly coupled frameworks Some frameworks let you go really quickly by coupling directly to them. You probably won't be able to reuse your code without considerable effort. —Drupal —Magento —Wordpress
  29. 29. More coupled framworks Some frameworks let you go faster when you adopt their conventions. You can reuse your code with a fair amount of additional effort. —Symfony (1) —CakePHP —Laravel
  30. 30. More decoupled frameworks Some frameworks encourage decoupling so your code is more reusable. You will go a little slower because you need to explicitly configure things —Symfony 2+ —Zend Framework 2+
  31. 31. Very decoupled frameworks Some frameworks are extremely decoupled so code is almost entirely reusable. You almost have to construct the entire framework yourself from components - this can be hard! —D.I.Y. —Silex —Zend Expressive
  32. 32. Decoupling inside your system
  33. 33. Only decouple where you need to (how do we know where that is?)
  34. 34. Coupled code get painful when change happens Decoupled code was wasted effort when change doesn't happen
  35. 35. Where does change come from?
  36. 36. Where does change come from? People!
  37. 37. Organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations — Melvin Conway, 1967
  38. 38. Decouple your system to respond to different streams of change
  39. 39. Service-orientation —Good abstractions help you define boundaries —Abstractions inside a monolith are easier to move when you get it wrong —Share values, not entities —Don't share persistence
  40. 40. Context mapping —Identify subdomains —Identify which are: —Core subdomains —Supporting subdomains —Generic subdomains —Mirror the structure in your architecture
  41. 41. The bad news: You will get it wrong You only find out afterwards
  42. 42. The good news: It's not just you
  43. 43. Things to check out —Context Mapping —Hexagonal Architecture —Modelling by Example
  44. 44. Thank you! —@ciaranmcnulty —Lead Maintainer of PhpSpec —Trainer and Coach at Inviqa Questions?

×