Brownfield Architecture transformations

Architectural changes in existing systems are tough. This presentation talks about various techniques that can be used demonstrated in 3 different projects

Transcript

1. Brownfield Architecture Transformations Arnon Rotem-Gal-Oz
2. Agenda Preface Chapter 1: The switcheroo rescue Chapter 2: the switch - IRL Chapter 3: the hard parts Chapter 4: Crape diem Epilog
3. Before - Motivation - After - Learnings/techniques - Why
4. There are no BEST practices
5. Chapter 1: The Switcheroo Rescue
6. Before
7. Motivation
8. After
9. Why was it possible?
10. Chapter 2 The switch IRL edition
11. Before
12. Motivation
13. After
14. The great migration
15. Throwaway prototype
16. Writers/Readers
17. Shadow mode
18. Feature flags / Gradual release
19. Why was it possible?
20. Increased cost and complexity during transition period
21. Chapter 3: The hard parts
22. Before
23. Motivation
24. (Ideal) After
25. Strangler-fig Pattern (Martin Fowler)
27. Services vs. Aspects
28. Readers/ Writers
29. Increased complexity (sometimes cost) during transition period
30. Chapter 4: Carpe Diem
31. A complex system that works is invariably found to have evolved from a simple system that works. John Gall, Systemantics (1977)
32. “The only constant is change” Heraclitus (6th century)
33. modularity
34. Module Distinct part of a system that performs some function and hides its inner workings from the rest of the system (~ David Parnas, 1972)
35. The microservices soup
36. High Cohesion Loose Coupling
37. Versions, versions everywhere API, data,
38. Interfaces/API centric
39. Epilogue
40. “The only constant is change” Heraclitus
41. There are no best practices only patterns in context