Skip to content

MQTT republishing is a performance bottleneck #67

@freol35241

Description

@freol35241

In order to separate incoming and outgoing MQTT traffic, pontos-hub makes use of two root topics: PONTOS_INGRESS and PONTOS_EGRESS. Incoming messages to PONTOS_INGRESS gets duplicated and republished onto PONTOS_EGRESS.

The main reason for this design is the lack of proper acl filtering for every message (ACL is only applied on SUBSCRIBE event), see for example: emqx/emqx#2936

However, to maintain ordering guarantee between messages on the MQTT bus, the republishing can not be parallelized, thus introducing a performance bottleneck.

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