Very good and engaging speaker.
I completely disagree however with some of the topics presented, especially with the "Commands should be in the Domain layer" as CQRS is an application level pattern and has nothing to do with the Domain Model & Events (which is also a different pattern). In applications where you don't want to do CQRS (you have services instead of commands&handlers) you can still have Domain Events. What happens in this case where you don't have commands? Do you have an incomplete or wrong domain model then? This does not make sense. Commands have nothing to do with the domain.
Great talk, although I feel like there was a LOT of content in here. Also, some explanations earlier on of terminology might've helped as these still confuse me a bit, but that may just be my brain :)
Good talk spiced up with some humor, which always helps to keep the attention. The approach sounds all very good, but most of us are at least somewhat stuck to legacy code and I would have liked some insight in how to add event sourcing to existing projects.
Again, great talk.
Still at the end you said "use only event sourcing if your business requires it", and I would like to hear about some examples.
Besides that, great job!
It bugged me out there was no basic explanation about the subject, and there was some expectation everyone knew. I thought Id go to this talk and get the good the bad and the complicated.
rest of the talk was quite clear and explained a bit, but did not really help a lot, because it was quite technical withouth background
> What happens in this case where you don't have commands? Do you have an incomplete or wrong domain model then? This does not make sense. Commands have nothing to do with the domain.
If you abstract the CQRS+ES stack into just functional composition patterns, you'll notice that the aggregate is actually the superfluous bit, and the command and events are core to your domain. Your assertion depends strongly on the context, don't think in absolutes.
> It bugged me out there was no basic explanation about the subject, and there was some expectation everyone knew. I thought Id go to this talk and get the good the bad and the complicated.
I didn't cover any basics mostly because both the keynote and a previous talk covered those. Therefore, I skipped fast-forward to the bits that we had to deal with, post-hello-world, basically.
I'll try factoring in descriptions for every concept that I mention, thanks :-)
One of my favorite talks on DPC. Speaker skills level 10/10, knowledge 10/10 and example with shooting in bar was probably the best explanation of Event Sourcing idea I saw.
I know your feelings about remote pilot, I'm fighting with the same issue...
Not just yet another talk on Event Sourcing. Also not theoretical at all. Very comprehensive journey through the speaker's own practical experience with the approach. Very down to earth and honest. Plenty of illustrated clean and clear examples that made it easy for me to follow. I specially like the later part for the presentation in which Marco shares what didn't work, what he learned with the whole experience. Nice one!
Although I think it might help to explain a bit more about event sourcing and cqrs itself, explain the basic concepts in a few slides, instead of spreading it over the entire presentation, as it otherwise makes it hard for people to understand how some of the examples are related to the concepts.
Nice presentation. Good speaker and interesting topic! Too bad there was little time left at the end. It looked to me like there were more people with questions and there was a beginning of what could have been an interesting discussion about commands.
Marco did an extremely good job of describing the process he went through at code-reviews.io. If anything, there was a bit too much that he covered in a mere 45 minutes. Covering the same amount of information in an 60 or even 75 minutes would allow it to land with the audience a bit better, imho. The topic deserves it.
Comments
Comments are closed.
Excellent
Very good and engaging speaker.
I completely disagree however with some of the topics presented, especially with the "Commands should be in the Domain layer" as CQRS is an application level pattern and has nothing to do with the Domain Model & Events (which is also a different pattern). In applications where you don't want to do CQRS (you have services instead of commands&handlers) you can still have Domain Events. What happens in this case where you don't have commands? Do you have an incomplete or wrong domain model then? This does not make sense. Commands have nothing to do with the domain.
Great talk, although I feel like there was a LOT of content in here. Also, some explanations earlier on of terminology might've helped as these still confuse me a bit, but that may just be my brain :)
Good talk spiced up with some humor, which always helps to keep the attention. The approach sounds all very good, but most of us are at least somewhat stuck to legacy code and I would have liked some insight in how to add event sourcing to existing projects.
Again, great talk.
Still at the end you said "use only event sourcing if your business requires it", and I would like to hear about some examples.
Besides that, great job!
It bugged me out there was no basic explanation about the subject, and there was some expectation everyone knew. I thought Id go to this talk and get the good the bad and the complicated.
rest of the talk was quite clear and explained a bit, but did not really help a lot, because it was quite technical withouth background
> What happens in this case where you don't have commands? Do you have an incomplete or wrong domain model then? This does not make sense. Commands have nothing to do with the domain.
If you abstract the CQRS+ES stack into just functional composition patterns, you'll notice that the aggregate is actually the superfluous bit, and the command and events are core to your domain. Your assertion depends strongly on the context, don't think in absolutes.
> It bugged me out there was no basic explanation about the subject, and there was some expectation everyone knew. I thought Id go to this talk and get the good the bad and the complicated.
I didn't cover any basics mostly because both the keynote and a previous talk covered those. Therefore, I skipped fast-forward to the bits that we had to deal with, post-hello-world, basically.
I'll try factoring in descriptions for every concept that I mention, thanks :-)
Great speaker! This was by far the best "event sourcing" talk during the conference!
Great talk, very well represented also I have taken a lot from this talk.
Very good talk, learned a lot from this (i think)
One of my favorite talks on DPC. Speaker skills level 10/10, knowledge 10/10 and example with shooting in bar was probably the best explanation of Event Sourcing idea I saw.
I know your feelings about remote pilot, I'm fighting with the same issue...
Not just yet another talk on Event Sourcing. Also not theoretical at all. Very comprehensive journey through the speaker's own practical experience with the approach. Very down to earth and honest. Plenty of illustrated clean and clear examples that made it easy for me to follow. I specially like the later part for the presentation in which Marco shares what didn't work, what he learned with the whole experience. Nice one!
Great talk, entertaining and informing.
Although I think it might help to explain a bit more about event sourcing and cqrs itself, explain the basic concepts in a few slides, instead of spreading it over the entire presentation, as it otherwise makes it hard for people to understand how some of the examples are related to the concepts.
I enjoyed this talk a lot. The slides where hilarious and the talk reflect honest experience with building an event-sourced application.
Great to see how CQRS+ES are used in a real app.
I your talk you mentioned that you would share the code, where can I find it?
Nice presentation. Good speaker and interesting topic! Too bad there was little time left at the end. It looked to me like there were more people with questions and there was a beginning of what could have been an interesting discussion about commands.
Marco did an extremely good job of describing the process he went through at code-reviews.io. If anything, there was a bit too much that he covered in a mere 45 minutes. Covering the same amount of information in an 60 or even 75 minutes would allow it to land with the audience a bit better, imho. The topic deserves it.
Well done! I can't see anything you can improve except remote pilot ;)
Great talk packed with info. Could maybe use a few jokes to make it less intense :)