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.


Comments are closed.

Good mix of tech vs organisational. It's now skewed, I feel, mostly towards problem discovery and explaining the environment (about 2/3) and less towards the solution (1/3 maybe) whereas I'd like to see it the other way around. You touched on "rewriting history" with the questions; I think that's an interesting topic that you could actually include in the slides, sort of a "what goes wrong but you can fix like this". The theoretical part is good but a little more from the practical side would make it more interesting for me. Nice presentation skills, like the minimal slides.

Good talk, interesting topic. Like the other commenter said: the sketch of the problem/situation (legacy project, basic architecture) was the longer part of the talk: that is a more general topic that everybody recognizes and definitely reaches the bigger crowds. It was good but I would also enjoy more emphasis on the second part where you focused on your projects solution using Kafka. That really inspired me to learn more about logging en event driven design, so I spent a good part of my day googling about it ^^.

As always your presentation was well done and clear for the broader public.

I really enjoyed the talk. Amazing mastery of domain, short slides, nice step-by-step presentation, concise, straight to the point. The only tip for the next, as the guys told above, would be to focus more on the pos instead of the pre. You divided your talk in two moments, talking first about how it was before, and then how you solved the problem. I think you should focus more on the second part, on the solution itself. But in general, congratulations for the nice talk.

Great to hear about database heavy legacy applications, and how to expose data from it with seemingly impossible project boundaries. While there was a lot of information about "project introduction", it would be great to hear more about critical management decisions that were made during the project. If you now look back, what management decisions that are typical for such legacy applications did really impact the project, both positive and negative.