Can anybody explain how there new license works? It doesn’t make sense why you could not now offer KSQL as a service, does that mean they can go after AWS for there Managed Kafka now? Link - https://www.confluent.io/blog/license-changes-confluent-platform
Clearly follows AWS's Kafka as a service announcement. They are, understandably, worried about Amazon or any cloud provider using their open source code and selling it as a managed service. I am curious if anyone knows how they are doing, I have been considering interviewing at confluent.
So essentially they updated the license, does that mean using older releases aside from the newer ones are affected by it? Or is it retroactive? Essentially can AWS just do an internal fork of a version and update it internal while still offering it as Managed Service? Also it’s interesting have any other companies done this were they essentially built there company around a open source project? Datastax/Databricks?
The blog post was crazy defensive and to me came off as a bit unhinged. “We are doing great and making lots of money! But we didn’t do it because of money! We don’t care about money! But we can’t let people take our money! We are doing great!” I wouldn’t interview there.
@blizzard, no Idea. @variant, well it's subjective. I haven't followed Jay or anyone in the confluent team closely, but Jay does across as very genuine and honest, at least to me.
Kafka hasn't been relicensed. Only KSQL was. It's not retroactive so you can continue to use old versions under the old license.
Maybe you should use stack overflow or hacker noon