Skip to content

add message handler #6

@piccione99

Description

@piccione99

The message handler is the "splitter".

The consumer consumes all messages from a "raw" kafka broker which contains all wrp messages from talaria.

At the very least splitter must be able to route message based on

  1. event type in the destination
  2. device id

The splitter should optionally be able to filter from multiple criteria for a given output stream: For example, both event type and device id. (caduceus currently has this functionality)

Ideally, the criteria should be generic and match any part of the wrp message for flexibility (but is not a hard and fast requirement - caduceus currently matches on event type and/or device id)

A wrp message MAY match multiple output streams.

The splitter must contain configurable buffering, retries and QOS based on the wrp message.

the wrpkafka library already handles a lot of this. What it's currently missing:

  1. a message is only sent to the first matching stream, therefore it can only be written to one stream
  2. it does not currently look like handles filtering on device id (double check this)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions