Parse Message Properties for Converter Consideration

[adeutscher]

Researching for an applied project pointed out that some applications may want to just route messages and not necessarily perform potentially-expensive deserialization of the main message body. RabbitMQ properties were specifically mentioned.

I'm going to see how this project plays out before I make any changes to the template, but making this issue as a reminder to consider it.

Action items:

• Add a Properties dictionary to the raw job model, as an item for consideration when converting to a job model.

[adeutscher]

Mr. Google's C# example of how sending to RabbitMQ with properties would work, for consideration in a RabbitMQ implementation:

using RabbitMQ.Client;

var props = new BasicProperties
{
    // 1. Tell consumers how to deserialize the outer envelope
    ContentType = "application/json", 
    
    // 2. Tell consumers how to interpret the internal arbitrary payload
    Type = "ExampleFormat", 
    
    // 3. Keep messages safe on disk if the broker restarts (as opposed to Transient keeping messages in memory).
    DeliveryMode = DeliveryModes.Persistent 
};

// Add custom headers if you plan to use a Headers Exchange for routing
props.Headers = new Dictionary<string, object>
{
    { "SourceType", "Example" }
};

// Publish the wrapper byte array
await channel.BasicPublishAsync(exchangeName, routingKey, mandatory: true, props, data);