Live data from Hacker News

MQTT vs. Kafka: An IoT Advocate's Perspective

influxdata.com

121–122 of 122 posts

Re: MQTT vs. Kafka: An IoT Advocate's Perspective

#121

Earlier quoted context omitted.

Got it - I think for the first 1-2 years one broker instance should be plenty. So the decision to up the complexity can probably be postponed to the point where it becomes clear that we hit 10M+/lots of brokers will be required.

Definitely. Focus on solving the business problem first, grow the business. When you have the need to make a switch, you will find a way forward by rebuilding your your MQTT infrastructure to fit your scale. If you ever need to.

Yeah - business is smart home renewable energy stuff, not lightbulbs. If they don't go international real fast the small oldschool broker cluster solution will probably be plenty for the next 5 years.

Re: MQTT vs. Kafka: An IoT Advocate's Perspective

#122
post #59

Earlier quoted context omitted.

Have you tried Pulsar or Redpanda? Both seem mature enough and provide decent performance to probably meet your needs. What I hear is that Redpanda is a lot easier to manage than Kafka.

What's the license for Redpanda? I couldn't find anything but maybe it's because I'm on mobile.

Disclaimer, I work at Redpanda.

Redpanda Community Edition is licensed with the Redpanda Business Source License (BSL). The core features are free and source-available.

This license was inspired by MariaDB and CockroachDB and "for 99.999% of users, restrictions will not apply". The big restriction is that users "cannot provide Redpanda as a commercial streaming or queuing service to others" which is primarily to deter large cloud vendors from taking our work and impacting our ability to operate as a business.

Here are some links for more details on how we came to this decision and how we license all our products and features.

https://redpanda.com/blog/bsl-source-available-license

https://docs.redpanda.com/docs/get-started/licenses/

Post reply on HN