seems reasonable and def simplifies the setup, also in terms of reduced footprint on regular-sized PCs. I also always noticed slighty faster creation-times for adapters in addition to pipeline deployment times.
Patrick > Am 14.02.2022 um 21:44 schrieb Dominik Riemer <[email protected]>: > > I need to check which version we are currently using 😉 > We've been supporting MQTT for quite a while where users can change the > preferred transport protocol from Kafka to MQTT, so I'd guess we are on v3. > I'll look into this...thanks for the hint to sparkplug! > > Cheers, > Dominik > > > -----Original Message----- > From: Christofer Dutz <[email protected]> > Sent: Monday, February 14, 2022 6:46 PM > To: [email protected] > Subject: RE: Making MQTT the default protocol? > > Which version? > > 3.x or the more moden 5.x (I would suggest to adopt the newer version as with > sparkplug this will only bring benefits) > > Just my 5ct from the peanut-gallery ;) > > Chris > > -----Original Message----- > From: Lukas Ott <[email protected]> > Sent: Montag, 14. Februar 2022 18:08 > To: [email protected] > Subject: 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 >> >>
