Skip to content

Add Identity and Metadata to Messages #3

@Mulkave

Description

@Mulkave

In order to identify producers, it could be helpful to have a proprietary message object that includes the body (data) that is usually sent by the user. A better way to explain this is through an example:

Producer A sends a BowlerMessage or BowlerMessageBody where the AMQPMessage's body property is the message body itself. That message contains the body and other metadata in a JSON format as such:

{
    "created_at": "DATETIME",
    "send_at":  "DATETIME",
    "body": "ENCODED JSON USER DATA",
    "producer": {
        "ip": "192.168.0.1",
        "name": "Facebook Ads Service",
        "subject": "Facebook Ads Estimated Reach - Audience Size",
        "queue_name": "facebook_ads_estimated_reach"
     }
}

The above is just an example to illustrate the idea, names and structure may change.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions