Apidays London 2024 - Renovate to Innovate 5 by Rashmi Venugopal, Netflix

Renovate to Innovate: Fundamentals of Transforming Legacy Architecture
Rashmi Venugopal, Senior Software Engineer - Netflix

apidays London 2024 - APIs for Smarter Platforms and Business Processes
September 18 & 19, 2024

------

Check out our conferences at https://www.apidays.global/

Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8

Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io

Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/

Transcript

3. Growth Trajectories
4. What got you here…
5. …will not get you there.
6. What got you here will not get you there.
7. Takeaway 1 Legacy Systems are a byproduct of success
9. Build the muscle to transform legacy systems
10. Takeaway 1 Legacy Systems are a byproduct of success Takeaway 2 Transform legacy systems for long term success
11. Renovate to Innovate The Fundamentals of Transforming Legacy Architecture
12. Rashmi Venugopal
13. NETFLIX TEXT Agenda — Legacy Systems — What — Why — Technical Renovation — What — When — Strategies
14. First word when you think of Legacy?
15. NETFLIX TEXT
16. Legacy Systems -What
17. A system that is incapable of keeping up with business requirements. What is a Legacy System?
18. Symptoms of Legacy Systems — Substantial Complexity
19. Symptoms of Legacy Systems — Substantial Complexity — Organizational Complexity
20. Symptoms of Legacy Systems — Substantial Complexity — Organizational Complexity — Operational Complexity
21. Symptoms of Legacy Systems — Substantial Complexity — Organizational Complexity — Operational Complexity — Cognitive Complexity
22. Symptoms of Legacy Systems — Substantial Complexity — Decrease in Innovation Velocity
23. Symptoms of Legacy Systems — Substantial Complexity — Decrease in Innovation Velocity
24. Symptoms of Legacy Systems — Substantial Complexity — Decrease in Innovation Velocity
25. Symptoms of Legacy Systems — Substantial Complexity — Decrease in Innovation Velocity
26. Symptoms of Legacy Systems — Substantial Complexity — Decrease in Innovation Velocity — Degraded Quality of Experience
27. Symptoms of Legacy Systems — Substantial Complexity — Decrease in Innovation Velocity — Degraded Quality of Experience
28. Symptoms of Legacy Systems — Substantial Complexity — Decrease in Innovation Velocity — Degraded Quality of Experience
29. Symptoms of Legacy Systems — Substantial Complexity — Decrease in Innovation Velocity — Degraded Quality of Experience
30. Legacy Systems -Why
31. Why legacy systems exist? — Advancement in Technology
32. Why legacy systems exist? — Advancement in Technology
33. Why legacy systems exist? — Advancement in Technology — Bit Rot Theory
34. Why legacy systems exist? — Advancement in Technology — Bit Rot Theory
35. Why legacy systems exist? — Advancement in Technology — Bit Rot Theory
36. Why legacy systems exist? — Advancement in Technology — Bit Rot Theory
37. Why legacy systems exist? — Advancement in Technology — Bit Rot Theory — Law of Architectural Entropy
38. Why legacy systems exist? — Advancement in Technology — Bit Rot Theory — Law of Architectural Entropy
39. Why legacy systems exist? — Advancement in Technology — Bit Rot Theory — Law of Architectural Entropy
40. Do we proactively improve legacy systems?
41. Big Ball of Mud
42. Technical Renovation -What
43. The act of upgrading or replacing outdated systems and technology to improve system health What is Technical Renovation?
44. Where does refactoring fit in?
45. Refactoring
46. Technical Renovation
47. Disclaimer: Refactoring is valuable!
48. Technical Renovation -When
49. When is Technical Renovation appropriate? — Business driven renovation
50. When is Technical Renovation appropriate? — Business driven renovation
51. When is Technical Renovation appropriate? — Business driven renovation — Ecosystem driven renovation
52. When is Technical Renovation appropriate? — Business driven renovation — Ecosystem driven renovation
53. When is Technical Renovation appropriate? — Business driven renovation — Ecosystem driven renovation — Tech Debt driven renovation
54. When is Technical Renovation appropriate? — Business driven renovation — Ecosystem driven renovation — Tech Debt driven renovation
55. Takeaway 1 Legacy Systems are a byproduct of success Takeaway 2 Transform legacy systems for long term success Takeaway 3 Right tool for the problem: renovate vs refactor
56. Technical Renovation -Strategies
57. Strategies for Technical Renovation — Make it work, Make it right, Make it fast
58. Make it work, Make it right, Make it fast Make it work
59. Make it work, Make it right, Make it fast Make it right
60. Make it work, Make it right, Make it fast Make it fast
61. Strategies for Technical Renovation — Make it work, Make it right, Make it fast — Evolutionary Architecture
62. 1. Identify Fitness Functions Evolutionary Architecture
63. 1. Identify Fitness Functions Evolutionary Architecture Ref: Building Evolutionary Architecture, Neal Ford, Rebecca Parsons
64. 1. Identify Fitness Functions 2. Continuous Experimentation Evolutionary Architecture
65. 1. Identify Fitness Functions 2. Continuous Experimentation Evolutionary Architecture
66. 1. Identify Fitness Functions 2. Continuous Experimentation 3. Incrementation Changes Evolutionary Architecture
67. 1. Identify Fitness Functions 2. Continuous Experimentation 3. Incrementation Changes Evolutionary Architecture
68. Strategies for Technical Renovation — Make it work, Make it right, Make it fast — Evolutionary Architecture — Renovating while Innovating
69. Renovating while Innovating
70. Renovating while Innovating
71. Renovating while Innovating
72. Renovating while Innovating
73. Renovating while Innovating
74. Strategies for Technical Renovation — Make it work, Make it right, Make it fast — Evolutionary Architecture — Deprecation Driven Development
75. Deprecation driven development What are we losing gaining by deprecating
76. Deprecation driven development
77. Deprecation driven development
78. Strategies for Technical Renovation — Make it work, Make it right, Make it fast — Evolutionary Architecture — Deprecation Driven Development — Intentional Organization Design
79. Intentional Organization Design Innovation = Discovery + Innovation
80. Intentional Organization Design Conway’s Law: The structure of software will mirror the structure of organization that built it
81. Intentional Organization Design Design A Design B
82. Intentional Organization Design
83. Strategies for Technical Renovation — Make it work, Make it right, Make it fast — Evolutionary Architecture — Deprecation Driven Development — Intentional Organization Design
84. NETFLIX IMAGE Growth Mindset
85. Takeaway 1 Legacy Systems are a byproduct of success Takeaway 2 Transform legacy systems for long term success Takeaway 3 Right tool for the problem: renovate vs refactor Takeaway 4 Renovate, Reorient, Repeat
86. Questions?