This is an ad for Redpanda and it's BSL, please stay away
BSL?
Kafka on Kubernetes: What could go wrong?
11–20 of 29 posts
Re: Kafka on Kubernetes: What could go wrong?
#12It's always funny to see attacks comming from vendors which are struggling in the real life because of Kubernetes success.
Re: Kafka on Kubernetes: What could go wrong?
#13Re: Kafka on Kubernetes: What could go wrong?
#14I would recommend looking at Strmzi for running Kafka on K8S. It works well and addresses all the issues mentioned in this piece. There's no reason to switch to RedPanda because you're running Kubernetes. https://strimzi.io/
Totally agree, and it's really open source unlike redpanda. For me really anything else is better than redpanda and their BSL license
Re: Kafka on Kubernetes: What could go wrong?
#15Did I seriously just read through the very worst kind of fiction, business process fiction, just to be bait and switched with an ad for something that isn’t actually Kafka? I don’t even use Kafka or Kubernetes but I thought this might be an interesting look at the possible failure modes and how to handle them.
Re: Kafka on Kubernetes: What could go wrong?
#16Earlier quoted context omitted.
BSL?
Business source license = fakely open source
While still meeting most of the OSI criteria for being open source. It basically says "you can use the features covered by this license for most uses, except creating your own SaaS offering of this product", plus some of the typical boilerplate about ensuring the license travels with the code.
It's basically a license that was created in response to how Amazon has been operating, co-opting open source technologies (whose business models focused on creating SaaS offerings of their open source tech) and creating their own managed services, directly competing with the creators (Redis even called this out a few years ago when they changed their license, see https://techcrunch.com/2019/02/21/redis-labs-changes-its-ope...).
They also indicate that at some point the license will change to Apache 2 ( https://github.com/redpanda-data/redpanda/tree/dev/licenses ); it's BSL right now likely to give them enough legal protection to keep competitors who'd operate Redpanda as a SaaS away, while they build up the enterprise (paid) features (which has a separate, far more wordy, license). I'd imagine they'd look to make the switch when they feel they have enough value and customers of the enterprise features.
I don't work on open source, or anything licensed by BSI, and from such an outsider perspective you sound...very dogmatic.
Re: Kafka on Kubernetes: What could go wrong?
#17Re: Kafka on Kubernetes: What could go wrong?
#18It's always funny to see attacks comming from vendors which are struggling in the real life because of Kubernetes success.
I’m not sure how that connects to the blog post. Redpanda works fine with Kubernetes and I assume by vendor you mean them.
Re: Kafka on Kubernetes: What could go wrong?
#19This is an ad for Redpanda and it's BSL, please stay away
Something can be an ad and still be good content and a good product. While I don’t use redpanda in production I really appreciate it for local development. Where does all the hate come from?
Re: Kafka on Kubernetes: What could go wrong?
#20Earlier quoted context omitted.
Business source license = fakely open source
While still meeting most of the OSI criteria for being open source. It basically says "you can use the features covered by this license for most uses, except creating your own SaaS offering of this product", plus some of the typical boilerplate about ensuring the license travels with the code. It's basically a license that was created in response to how Amazon has been operating, co-opting open source technologies (w…
"The BSL is not an Open Source license and we do not claim it to be one."
"The BSL does not meet the Open Source Definition (OSD) maintained by the Open Source Initiative (OSI). OSD does not allow limitations on specific kinds of such, such as production use."
> Q: Can I use BSL products to develop software that will be licensed under different licenses? > > A: Yes, as long as you don’t include any of the BSL code in the code for the software that’s being developed, and you do not make production use of the BSL code.
From the creators of the BSL license[0]: https://mariadb.com/bsl-faq-adopting/
BSL is not open source, period. It's just another startup source-available license parading "I want to be open source on GitHub.. but gosh please don't use my code without paying me!!"
Companies should stop instructing Heather to create these licenses IMO, and just split their code into open source and enterprise-only parts. It's easier, more honest, and ends this whole debate. It's the GitLab/Sourcegraph model too.