Putting your events on a diet • Particular Software

Anybody can write code that will work for a few weeks or months, but what happens when that code is no longer your daily focus and the cobwebs of time start to sneak in? What if it’s someone else’s code? How do you add new features when you need to relearn the entire codebase each time? How can you be sure that making a small change in one corner won’t break something elsewhere?

This is a companion discussion topic for the original entry at https://particular.net/blog/putting-your-events-on-a-diet

I guess both commands and events are async. How do you ensure that commands are received by each service before the sale service had received the event?

It’s always possible for messages in a distributed system to arrive out of order. Check out our blog post You don’t need ordered delivery to find out how that works.