One of the biggest problems when dealing with legacy is any change to the software might break the old system. Refactoring is usually slow and dangerous. In this talk I will discuss how we successful migrated an ancient legacy project to an event-driven architecture using just the power of events and Kafka.
22. The Project
❖ Proprietary software
❖ Hacked on “solutions”
❖ Old hardware
❖ Business logic in SP: No version control
❖ Original Team members gone
❖ Unwilling supplier
23.
24.
25.
26. The Assignment
❖ Rebuild the Web Portal from scratch
❖ Decouple from the main system
❖ Make the data queryable without causing extra load
27. The Constraints
❖ Cannot change proprietary software easily
❖ Load excessively high: no additional load
❖ Real Time querying not an option
❖ Slow release cycles (quarterly)
❖ Time constraint
❖ Do not jeopardise production
47. Event-driven architecture (EDA), is a software
architecture pattern promoting the production,
detection, consumption of, and reaction to events.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
66.
67.
68.
69. Lessons learned
❖ Events give you a powerful way to decouple
❖ Events are very good contracts
❖ Event driven is a flexible architecture
❖ Making team think in terms of Events can be challenging
❖ Kafka is a very powerful tool but needs research
❖ Mistake are great learning moments
❖ Eventual Consistency is still a hard problem
