Summarizing "Can one command cause multiple events?"

The answer to Daniel’s question was spread out over quite a few calendar days. Today’s missive is just a collection of links to all the parts of the answer for your convenience:

  1. Reader question: Can one command lead to two events?
  2. Moving clams (?) with events
  3. Avoiding duplicate clam movement during transfers
  4. Message stores vs. message brokers
  5. Streams got a name
  6. How components collaborate
  7. Handling another component’s events
  8. You pulled a fast one on us!
  9. Wrapping “Can one command cause multiple messages?”

Like this message? I send out a short email each day to help software development leaders build organizations the deliver value. Join us!

Get the book!

Ready to learn how to build an autonomous, event-sourced microservices-based system? Practical Microservices is the hands-on guidance you've been looking for.

Roll up your sleeves and get ready to build Video Tutorials, the next-gen web-based learning platform. You'll build it as a collection of loosely-coupled autonomous services, developing a message store interface along the way.

When you're done, you'll be ready to contribute to microservices-based projects.

In ebook or in print.