Events are a vital part of Event-Driven Architecture, representing business facts that happened in our system. To integrate business workflow steps, we need to define the mapping between the code type representing our event and serialised message. We can use manual or convention-based approaches to define this mapping, depending on our preferences. We also need to consider the evolution/versioning of events when defining the mapping. In this article, Oskar Dudycz explains how we can get the best of both worlds, using conventions by default but also having the option to switch to manual mapping to account for changes in event type names. He also touches on the pros and cons of using text-based versus binary formats for serialisation. Overall, this article provides valuable insights into best practices for mapping event types in Event-Driven Architecture.
