Activities tie events together. Receiving an event triggers an activity that triggers downstream events. In this video, learn how about activities by adding them to your event map.
- [Instructor] Now let's look at the second flow … at the authorized shipment flow. … Once we've authorized the shipment, … of course the next event is going to be … that the shipment has been authorized. … So, we'll move this up here in order to indicate that. … There's some business rules involved though … is that the shipment can't be authorized. … Or rather the shipment can't be made … until we've received payment. … So I'd like to capture that business rule on the diagram … and I'm going to do that using a purple note, … a process note. … So let's go up here, … grab purple, … and I'm going to capture my business rule. … I cannot ship unless payment has been processed. … So that's a business rule. … It has to do with shipment authorized. … So I'll attach it here to the shipment authorized step. … Once the shipment has been authorized, … then I can create a shipping label. … So let's do that next. … We'll just cut and paste this guy. … Now the shipper is clearly going to be an external entity also. …
- How DDD differs from other architectural approaches
- How DDD fits with agile
- Advantages of microservices
- Bounded contexts and entities
- Reactive vs. declarative systems
- Using event storming to develop a DDD architecture