Chapter 3. An in-depth tour of message properties
This chapter covers
- Message properties and their impact on message delivery
- Using message properties to create a contract with publishers and consumers
In chapter 1, I detailed how I set out to decouple member login events from database writes that were causing delays for members logging into a website. The advantages of doing so quickly became clear to our entire engineering organization, and using a loosely coupled architecture for database writes took on a life of its own. Over time, we began to leverage this architecture in new applications we were developing. No longer were we just processing member login events, we were using this architecture for account deletions, email message generation, and any application event that could be performed asynchronously. Events were being published through the message bus to consumer applications, each performing its own unique task. At first we put little thought into what the message contained and how it was formatted, but it soon became apparent that standardization was needed.