So good afternoon everyone. My name is Robert Zaladek. I'm the Director of Business Development
for a company called AdaptX Solutions and we're experts in helping companies build event-driven
systems. And one of the approaches that we use with all of our clients is an approach
called event storming. So I want to tell you a little bit about it and also see how you
might use it in one of your upcoming projects. So what is it? Event storming is an approach
to modeling complex business flows. It's geared towards projects that leverage things like
domain-driven design and event sourcing, but it provides some insight no matter what approach
you use. The benefits of the approach are that it's fast, it's comprehensive, it's
really collaborative, it's efficient, and it's a lot of fun to do. So what do you need
to do event storming? Actually sorry, you know what, let me... So not only is it fast,
efficient, fun, and so on, but essentially what you get out the other side is you get
an outline of what you want to build, how it's going to fit into the existing product
and the exact sequence of how the new functionality will work. So essentially it gives you both
the business flow and an outline of the architecture. So what you need. So you need to get the
right people in the room. So traditionally when we develop new systems, you get a BA
or a product owner, somebody who comes around and goes and meets with all these different
stakeholders. This short-circuits that whole process. What it does is you get everybody
in the room at the same time. So you might have people like a developer, a team lead,
architect, product owner, BA, someone from sales as well as maybe a CEO in a smaller
company, and everybody gets involved. The approach allows you to think through events
from end to end because all the people are in the room at the same time from a variety
of disciplines and backgrounds, and none of the steps are missed. Edge cases are explored
and essentially you go from a blank slate to a fully-fledged sort of product outline
in a matter of hours. Okay, great. All right. This is actually what... This is what it looks
like, and this is what we're going to be doing downstairs afterwards. As you can see, it's
a very, very simple approach, and I'm just going to go right into what you need to think
through with these things. So what you want to do is start with domain events. A domain
event is something significant that happens in the domain. For example, payment processed,
and the use of the past tense is really, really important when you're doing this. You also
want to consider how the domain events came about. So in almost every case, there are
going to be events before, there are going to be events after, and this allows you to...
This approach allows you to move the stickies around in a very, very elegant way. Okay.
Thanks. Come downstairs and do an event starting with us.