Timeline for How to represent a loop in Event Storming?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 31, 2021 at 23:35 | comment | added | secondbreakfast | Wow, great answer thank you! So as an example: for every item in an order, a warehouse picker needs to locate and scan that item then load it on a rack. If I needed to model that process but show that it loops, perhaps I could model it once with the 🔁 next to it, then have an event that says "All items picked" or something? | |
| Mar 31, 2021 at 23:34 | vote | accept | secondbreakfast | ||
| Mar 30, 2021 at 21:24 | comment | added | Christophe | @MikeRobinson :-) I remember having worked with low level event loops, and it was indeed very tricky. Especially as not all the vents were completely independent. But domain events are at a very different level of abstraction. Moreover, in the storming workshop, the events are unrolled to make a chronological perspective that is really easy to understand. I don't think that it's a fatality to have unreadable code with event processing ;-) By the way, some CEP gurus pretend that every company is just an efficient distributed event processing engine. | |
| Mar 30, 2021 at 20:04 | comment | added | Mike Robinson | But ... "if this (koff, koff) old programmer might dare to say," far worse(!) than any "spaghetti code!" Don't design software this way. Your grandchildren will hate you for it. | |
| Mar 30, 2021 at 19:40 | comment | added | Rik D | Very good explanation! | |
| Mar 30, 2021 at 19:31 | history | answered | Christophe | CC BY-SA 4.0 |