Hi all, yes, I also really like the idea to use MQTT as the default protocol. I am in favor of Dominik's proposal to do the changes after the next release. @Dominik do you already have an idea how we could replace the features that are currently relying on Kafka?
I also think it makes sense to leverage the functionalities of MQTT5. Is there an expert in the community who can help with that? I think it would be great to talk about the conceptual possibilities and how we could integrate it properly into the StreamPipes architecture. The same goes for Sparkplug, I see a lot of advantages when ingesting data into StreamPipes, but also when we want to share analytics results to other systems. I am not sure if it makes sense to also use it for the internal communication. What do you think? I haven't done anything with it yet, does anyone have more experience with it? Philipp Am 18.02.22, 13:39 schrieb "Obermeier. Stefan" <[email protected]>: Hi Dominik, I like this idear Cheers Stefan -----Ursprüngliche Nachricht----- Von: Dominik Riemer <[email protected]> Gesendet: Donnerstag, 17. Februar 2022 22:00 An: [email protected] Betreff: RE: Making MQTT the default protocol? Hi Stefan, good point. We could add this also to the UI so that configurations can be changed. This is already available for Kafka under settings/messaging. So probably it would be good to consider this when switching to MQTT as the default option. Also, we would need to rethink the pipeline monitoring which currently only works for Kafka mode. On the other hand, I'd really like to release a new version soon. So what do you think about releasing the new version soon with Kafka, then focus on switching to MQTT with fully supported configurations and monitoring? This shouldn't be too much effort and it would be a good opportunity to switch to a bit shorter release cycle in general 😉 Cheers Dominik -----Original Message----- From: Obermeier. Stefan <[email protected]> Sent: Wednesday, February 16, 2022 1:57 PM To: [email protected] Subject: AW: Making MQTT the default protocol? +1 I think it could be interesting for some users to know the current or default configuration. E.g. QoS level, is a persistent session used ... I don't now what the best place could be. Possibly in the docs or UI? Stefan -----Ursprüngliche Nachricht----- Von: Lukas Ott <[email protected]> Gesendet: Montag, 14. Februar 2022 18:08 An: [email protected] Betreff: Re: Making MQTT the default protocol? +1 Am Mo., 14. Feb. 2022 um 18:01 Uhr schrieb Dominik Riemer <[email protected]>: > Hi all, > > for the next release, should we use MQTT as the default messaging > protocol of the standard installation? It seems most users are looking > for a rather lightweight initial installation, so we could provide the > default docker-compose file with MQTT instead of Kafka/zookeeper and > keep the Kafka integration for the "full" docker configuration. I > think this would reduce the overhead for first-time users. > What do you think? > > Cheers > Dominik > > SEEBURGER AG Vorstand/SEEBURGER Executive Board: Sitz der Gesellschaft/Registered Office: Axel Haas, Michael Kleeberg, Axel Otto, Dr. Martin Kuntz, Matthias Feßenbecker Edisonstr. 1 D-75015 Bretten Vorsitzende des Aufsichtsrats/Chairperson of the SEEBURGER Supervisory Board: Tel.: 07252 / 96 - 0 Prof. Dr. Simone Zeuchner Fax: 07252 / 96 - 2222 Internet: http://www.seeburger.de Registergericht/Commercial Register: e-mail: [email protected] HRB 240708 Mannheim Dieses E-Mail ist nur für den Empfänger bestimmt, an den es gerichtet ist und kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material enthalten. Jegliche darin enthaltene Ansicht oder Meinungsäußerung ist die des Autors und stellt nicht notwendigerweise die Ansicht oder Meinung der SEEBURGER AG dar. Sind Sie nicht der Empfänger, so haben Sie diese E-Mail irrtümlich erhalten und jegliche Verwendung, Veröffentlichung, Weiterleitung, Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt. Weder die SEEBURGER AG noch der Absender (Obermeier. Stefan) übernehmen die Haftung für Viren; es obliegt Ihrer Verantwortung, die E-Mail und deren Anhänge auf Viren zu prüfen. This email is intended only for the recipient(s) to whom it is addressed. This email may contain confidential material that may be protected by professional secrecy. Any fact or opinion contained, or expression of the material herein, does not necessarily reflect that of SEEBURGER AG. If you are not the addressee or if you have received this email in error, any use, publication or distribution including forwarding, copying or printing is strictly prohibited. Neither SEEBURGER AG, nor the sender (Obermeier. Stefan) accept liability for viruses; it is your responsibility to check this email and its attachments for viruses. SEEBURGER AG Vorstand/SEEBURGER Executive Board: Sitz der Gesellschaft/Registered Office: Axel Haas, Michael Kleeberg, Axel Otto, Dr. Martin Kuntz, Matthias Feßenbecker Edisonstr. 1 D-75015 Bretten Vorsitzende des Aufsichtsrats/Chairperson of the SEEBURGER Supervisory Board: Tel.: 07252 / 96 - 0 Prof. Dr. Simone Zeuchner Fax: 07252 / 96 - 2222 Internet: http://www.seeburger.de Registergericht/Commercial Register: e-mail: [email protected] HRB 240708 Mannheim Dieses E-Mail ist nur für den Empfänger bestimmt, an den es gerichtet ist und kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material enthalten. Jegliche darin enthaltene Ansicht oder Meinungsäußerung ist die des Autors und stellt nicht notwendigerweise die Ansicht oder Meinung der SEEBURGER AG dar. Sind Sie nicht der Empfänger, so haben Sie diese E-Mail irrtümlich erhalten und jegliche Verwendung, Veröffentlichung, Weiterleitung, Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt. Weder die SEEBURGER AG noch der Absender (Obermeier. Stefan) übernehmen die Haftung für Viren; es obliegt Ihrer Verantwortung, die E-Mail und deren Anhänge auf Viren zu prüfen. This email is intended only for the recipient(s) to whom it is addressed. This email may contain confidential material that may be protected by professional secrecy. Any fact or opinion contained, or expression of the material herein, does not necessarily reflect that of SEEBURGER AG. If you are not the addressee or if you have received this email in error, any use, publication or distribution including forwarding, copying or printing is strictly prohibited. Neither SEEBURGER AG, nor the sender (Obermeier. Stefan) accept liability for viruses; it is your responsibility to check this email and its attachments for viruses.
