As you advance in your career, you'll quickly fall into the "sequential tasks" trap. "I need to do these ten things when a user signs up.... but I have no idea where to place this logic." Many times, we give up and simply throw it in the controller. But is that the best place? Might there be a better way (when appropriate) to structure our applications? Sure! Let me show you.
In the opening episode, we'll review the "sequential tasks" dilemma, while introducing the concept of command objects.
Now that we have our first command object, we next need to calculate the appropriate handler class, which will delegate, as needed. Let's tackle that in this episode. Go sports!
So we've successfully translated a command into its associated handler class. In this lesson, we'll delegate, as needed, to post the job listing - while raising domain events in the process.
So, we've learned how to dispatch our custom events, but how do we go about listening for them? Well, in this lesson, I'll show you a really nice and clean way to go about it! Let's do this.
Now that our base is essentially complete, let's go through the process of, using our job site example, marking jobs as filled, or archived.
In this lesson, we'll extend the functionality of the command bus by adding a validation decorator, while also reviewing an implementation that uses simple inheritance.