In the age of pub/sub, sometimes you need a message to be distributed to multiple consumers based on topics but yet need the message to be treated with persistence and statuses (pending, active, delayed, failed & completed). This gave rise to CrimsonQ!
