Managing Legacy Tech Migrations

Talk at Tech Leadership Meetup | Amicus x Dojo on Tuesday 17th September 2024

https://www.eventbrite.co.uk/e/tech-leadership-meetup-amicus-x-dojo-tickets-976251613857

Transcript

1. @hpoom Managing Legacy Tech Migrations Tech Leadership Meetup | Amicus x Dojo
2. @hpoom About me Director of Software Engineering Simon Wood
3. What Collinson does for our customers PRIORITY PASS™ The most recognised airport lounge and experiences programme
4. Approach What I am going to cover What is Legacy? Technology
5. @hpoom Legacy? What is
6. @hpoom AGE is not the only factor
7. @hpoom Unstable or Expensive
8. @hpoom Risk is to high
9. @hpoom Can not Innovate
10. @hpoom Approach
11. @hpoom CULTURE can be your biggest blocker
12. @hpoom Content slide. GOV.UK https://bit.ly/32dOXsR
13. “an unwillingness to change current processes and ways of working may limit your ability to change legacy technology”
14. ” @hpoom It’s not the strongest, fi ttest or most intelligent that survive, it’s the ones that are best able to adapt to change. GCHQ Source: https://github.com/gchq/BoilingFrogs
15. @hpoom LEAN approach is the only way
16. ” @hpoom When eating an elephant take one bite at a time. Creighton Abrams “Big 5 Elephant" by Caitlin. Licensed under Creative Commons.- https:// fl ic.kr/p/b8hYD
17. @hpoom Fake it till you make it build
18. @hpoom
19. @hpoom BUILD and you will FAST learn fast
20. ” @hpoom Move fast and break things. Unless you are breaking stu ff , you are not moving fast enough. Mark Zuckerberg Source: https://of fi cesnapshots.com/2013/02/04/facebook-menlo-park-of fi ce-design/
21. @hpoom Continuous Improvement
22. @hpoom Technology
23. @hpoom MICRO SERVICES small is always better
24. ” @hpoom Small Autonomous services that work together, modelled around a business domain. Sam Newman "Sam Newman" by Gavin Bell. Licensed under Creative Commons.- https:// fl ic.kr/p/LEwhq
25. @hpoom Single Responsibility
26. Independently Scaleable Benefits of Microservices High Testability Technology Diversity Independently Deployable
27. @hpoom TOOLING to help you succeed
28. @hpoom Dependencies
29. Know all the touch points into your legacy Use standards and common data types Interactions APIs Abstraction Manage your dependancies Put everything behind an API
30. @hpoom Strangler Pattern
31. Routing Routing Modern Tech Modern Tech Legacy Tech Legacy Tech Modern Tech Early phase Later phase Migration Complete
32. Develop the new service independently Move all consumers to the new service and remove old code Transform Co-Exist Eliminate Strangler Pattern in practice Let both New and Old solution exist side by side
33. @hpoom Traffic Shadowing
34. Service or UI User Old Service New Service Send request to both Compare the response
35. @hpoom Content slide. Compare https://bit.ly/2PcyShI
36. @hpoom OBSERVABILITY data & metrics are everything
37. ” @hpoom If Engineering at Etsy has a religion, it’s the Church of Graphs. If it moves, we track it. Sometimes we’ll draw a graph of something that isn’t moving yet, just in case it decides to make a run for it. Code as Craft "Etsy" by KnitSpirit. Licensed under Creative Commons.- https:// fl ic.kr/p/btwyFm
40. @hpoom
41. Consider Approach So to recap… Identify Legacy Use Established Patterns
42. @hpoom Thank you please contact me if you have any questions By Simon Wood