Feature Request
We would like to automate forwarding iot-data to our customers, which sometimes want to recieve those informations via webhook or via mqtt.
Motivation
We currently have 2 systems publishing data to webhook as batches and to eclipse-mosquitto mqtt server seperatly, managing customers credentials for this server as well.
Proposal
We would like to suggest to eigher integrate the eclipse-mosquitto mqtt server itself into svix and allowing application owners to map data into their own topics like v1/applicationId/d/topicNameBasedOnWebhookDateOrStatic.
AND/OR
define publishing data to publish the data to an external mqtt server.
If you descide to use the mqtt broker within the product I suggest using a plugin like moquitto-go-auth to integrate nativly into svix platform and to handle authentication like user: applicationId, pass: comes from svix db and has to be defined by api f.ex. via the portal
acl could be set to v1/applicationId/d/#
Alternatives
like our currently duplicated aproach
Notes
We dont know 100%, how streams are working currently, maybe thats similar or has overlaps.
We would understand, if thats not the target of Svix, but we considdered it worth mentioning as, it could be a huge new USP :)
And would reduce maintenance on our part :)
Thanks yall :)
Feature Request
We would like to automate forwarding iot-data to our customers, which sometimes want to recieve those informations via webhook or via mqtt.
Motivation
We currently have 2 systems publishing data to webhook as batches and to eclipse-mosquitto mqtt server seperatly, managing customers credentials for this server as well.
Proposal
We would like to suggest to eigher integrate the eclipse-mosquitto mqtt server itself into svix and allowing application owners to map data into their own topics like v1/applicationId/d/topicNameBasedOnWebhookDateOrStatic.
AND/OR
define publishing data to publish the data to an external mqtt server.
If you descide to use the mqtt broker within the product I suggest using a plugin like moquitto-go-auth to integrate nativly into svix platform and to handle authentication like user: applicationId, pass: comes from svix db and has to be defined by api f.ex. via the portal
acl could be set to v1/applicationId/d/#
Alternatives
like our currently duplicated aproach
Notes
We dont know 100%, how streams are working currently, maybe thats similar or has overlaps.
We would understand, if thats not the target of Svix, but we considdered it worth mentioning as, it could be a huge new USP :)
And would reduce maintenance on our part :)
Thanks yall :)