Raw Message Delivery Options

[slang25]

Morning all. Currently when we publish a message via SNS, we don’t use raw delivery, so our message is wrapped in an SNS message type. When we publish “point-to-point”, i.e. straight to a queue, we follow a similar pattern of double encoding the underlying message:

{
    "Subject": "OrderAccepted",
    "Message": "{\"OrderId\":1234,\"Id\":\"e3f84a55-b677-43df-8c24-92c170fdd89f\",\"TimeStamp\":\"2019-07-03T09:53:09.2956149Z\",\"RaisingComponent\":\"orderapi\"}"
}

Which is a subset of the SNS message format.
I was thinking about how we might want to support raw messages, what do people think about simply having the Message property contain the message object, rather than a serialized string of it. On deserialization we’d just check the type of the Message property, so there would be no configuration on the receiving side (if you use JustSaying), other consumers would need to understand this pattern.

So this above example becomes:

{
    "Subject": "OrderAccepted",
    "Message": {
        "OrderId": 1234,
        "Id": "e3f84a55-b677-43df-8c24-92c170fdd89f",
        "TimeStamp": "2019-07-03T09:53:09.2956149Z",
        "RaisingComponent": "orderapi"
    }
}