Practical Microservices

Naming Messages

Giving types to our messages is the most important of the engineering work we’ll do. As we add features to our system, we’ll use messages to represent the various processes the system carries out. The preceding messages come from the video cataloging process we’ll build in Chapter 10, ​Performing Background Jobs with Microservices​.

We come up with types for the messages in collaboration with our company’s business team. Message types are named after the business processes they represent. Furthermore, we select types using language familiar to experts in the domain we are modeling. This is not something we can do alone as developers.

If we were modeling banking, we might have messages like TransferFunds, AccountOpened, and ...