Our application has so much going on! Slow page loads and a large legacy codebase make developers feel stuck between a rock and a hard place. In this session, we will explore a strategy to add a modern codebase alongside the legacy code, allowing them to run simultaneously until you replace it. We will discuss common legacy problems like complex database queries causing slow downs and large reports that take so long to load, users must wait instead of analyzing the data. As our system has grown, we may need to separate our application into distinct parts and pass relevant information between them. Or maybe we have two distinct codebases already and each codebase is affected by the other's changes in ways we didn't expect. We will examine how to add Event Sourcing and CQRS to these pain points and throw away that legacy spaghetti!


Comments are closed.

Bit sad that there were technical issues with the presentation, because speaker has a lot more to offer. Could use some more ES and CQRS examples, as general feeling is that this is what talk is based on.

Robert Basic at 07:40 on 29 May 2018

Finally a bit different take on event sourcing! Not one, not even two, but three! examples how event sourcing is used to improve the quality of applications.

I've always felt that such dramatically different approaches as event sourcing and CQRS would require either engaging in a full rewrite or starting with them in the beginning of the project. However she showed three examples of adding value to existing projects using them.

It's quite unfortunate that the slides didn't work as expected and the code examples were very hard to read, especially from the back rows.

Tomo Šala at 13:24 on 14 Jun 2018

Although Emily encountered technical problems mid presentation, she managed to overcome them like a pro - doing her best to keep the audience engaged and focused.

This gave a bit different take on CQRS&ES, not focusing on code and implementation as much as on giving context and insight into the different aspects of applicability of CQRS&ES in various parts of the existing applications.

Emily has clear diction and great vocabulary.