Viewing profile — boredandroid

In my opinion this is pre-cloud thinking. It used to be that distributed systems were a big trade off. They were operationally complex, they had limited apis (NoSQL), but they scal…

At my last startup, things would have been far less dysfunctional if the leadership team had read (and adopted) this philosophy. When we got backed by Venture funding it basically …

This is Jay, the CEO of Confluent. No, actually quite the opposite. We took pains to ensure that the license was written so that software products like Landoop were free to embed o…

This is Jay Kreps, I'm the CEO of Confluent. The license is actually not a EULA, that is a misunderstanding. We have added this item to our FAQ: https://www.confluent.io/confluent-…

Confluent continues to fund the development of quite a lot of Apache 2.0 code and that is a huge part of our business and strategy. Perhaps your point is that if a company produces…

I can address some of the critiques that seemed aimed at the blog post I wrote announcing the Confluent license change: 1. We aren't trying to get cloud providers to license our pr…

We address that here: https://www.confluent.io/confluent-community-license-faq Short answer: 1. AGPL doesn't actually solve this problem. This is why MongoDB just moved away from A…

Sure, I've updated the post so it doesn't imply that we comply with the OSI open source definition.

Thanks!

This is a great question. Many people think the AGPL solves this problem but it absolutely does not. This is why MongoDB, which was AGPL licensed, just changed to a custom license.…

I agree that the proliferation of new licenses is annoying. But I think the reason you see changes in licensing from Elastic, MongoDB, etc is that the world has changed pretty dram…

No, this has no effect on Kafka, which is part of the ASF and under the Apache 2.0 license. This just impacts things like KSQL that are part of Confluent Platform.

Hi all, I'm Jay Kreps, the CEO of Confluent and author of that blog post. I'm happy to answer any questions.

Yes the idempotence part of this feature set is very similar to TCP (the transactional consumption and updates obviously aren't). But this isn't a reimplementation at all. TCP prov…

That is part of it but there is also a general purpose transaction feature that lets you link together updates, state journalling and consumption all in a single transaction. This …

To clarify: the transaction feature is a transaction over updates to Kafka and provides transparent, correct processing in Kafka for Kafka Streams or anything else only maintaining…

Dear hacker news: 1. Please read the section entitled "Is this Magical Pixie Dust I can sprinkle on my app?" Before making angry comments. Answer: for general consumer apps just co…