Successfully reported this slideshow.
Your SlideShare is downloading. ×

Integration Design (by Lee Simpson)

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad

Check these out next

1 of 26 Ad
Advertisement

More Related Content

Slideshows for you (20)

More from Daniel Toomey (20)

Advertisement

Recently uploaded (20)

Integration Design (by Lee Simpson)

  1. 1. 2018 - Brisbane GLOBAL INTEGRATION BOOTCAMP Lee Simpson Integration Design
  2. 2. GLOBAL INTEGRATION BOOTCAMP
  3. 3. Development Trade-offs
  4. 4. Design Trade-offs
  5. 5. GLOBAL INTEGRATION BOOTCAMP
  6. 6. Eggs!
  7. 7. GLOBAL INTEGRATION BOOTCAMP
  8. 8. API Layers Experience APIs / Channel Adapters Process APIs / Business Services Core Systems System APIs / Product Adapters Gateway OOTB System Integration 1 2 3 4 MoreReusable Flexible,easyto change
  9. 9. GLOBAL INTEGRATION BOOTCAMP
  10. 10. Core Integration Capabilities - Telephone Synchronous
  11. 11. Core Integration Capabilities- Letter Asynchronous
  12. 12. Core Integration Capabilities - Subscription Publish - Subscribe
  13. 13. GLOBAL INTEGRATION BOOTCAMP
  14. 14. Requirements
  15. 15. Requirements
  16. 16. Requirements
  17. 17. Requirements
  18. 18. Requirements
  19. 19. Requirements
  20. 20. Design
  21. 21. Technology View
  22. 22. Tool

Editor's Notes

  • Automated
    – time it takes to automated (opportunity cost) - example – first few sprints
    I believe the how to build is now scriptable – locked in knowledge at a point in time – what if team or software changes
    Example of people changing how the build process worked
    Don’t automate something until its boring
    You understand it
    Make mistakes
    Delivery is the thing, not automation


    Manual allows – human side of testing – Exploratory testing, how can I break this
    Automation – great for subtle tests – not obvious ones

    Test driven – write all tests of feature (effective)
    TDD – efficient,

    Assume everything is a spike – until it proves itself - (Spike and stabilize)

  • Premature components
    Deign as a garden – let it grow a bit wild – you start to see the patterns – domain model will emerge – different to what you may think up front
    Components introduce complexity – what do you get?

    Message based – anything that may take time but complex (call-backs, ordering etc)
    Resource – quick to do

    DRY – things end up not being the same. Dependency issues. Coupling -

    Domain model – Customer means different things in different contexts
    DNA – copy paste – evolve.

×