boredandroid

6 ms·

1.
by boredandroid 6y ago
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 scaled. The best solution used to be to build things using a non
2.
Streams and Tables in Apache Kafka: A Primer(confluent.io)
1 points by boredandroid 7y ago|0 comments
3.
by boredandroid 8y ago
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 forced us into rapid scaling that we weren't prepared f
4.
Confluent Raises a $125M Series D Funding Round(confluent.io)
3 points by boredandroid 8y ago|0 comments
5.
by boredandroid 8y ago
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 our open source and compete with us in that way. This FAQ cov
6.
by boredandroid 8y ago
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-community-license-faq
7.
A Quick Comment on Bryan Cantrill’s Blog on Licensing(medium.com)
5 points by boredandroid 8y ago|0 comments
8.
by boredandroid 8y ago
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 any non-open source code they are not an open source compan
9.
by boredandroid 8y ago
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 proprietary features. We run a cloud service of our softw
10.
by boredandroid 8y ago
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 AGPL. 2. AGPL is quite restrictive for
11.
by boredandroid 8y ago
Sure, I've updated the post so it doesn't imply that we comply with the OSI open source definition.
12.
by boredandroid 8y ago
Thanks!
13.
by boredandroid 8y ago
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. The other reason we don't want to use AGPL is that it
14.
by boredandroid 8y ago
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 dramatically since most of the original licenses were created. T
15.
by boredandroid 8y ago
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.
16.
by boredandroid 8y ago
Hi all, I'm Jay Kreps, the CEO of Confluent and author of that blog post. I'm happy to answer any questions.
17.
Of Streams and Tables in Kafka and Stream Processing(michael-noll.com)
2 points by boredandroid 8y ago|0 comments
18.
Using Kafka's Streams API for Real-Time, Predictive Ad Computations at Pinterest(medium.com)
4 points by boredandroid 9y ago|0 comments
19.
It’s Okay to Store Data in Apache Kafka(confluent.io)
41 points by boredandroid 9y ago|5 comments
20.
Notes on Exactly-Once Support in Apache Kafka(medium.com)
7 points by boredandroid 9y ago|0 comments
21.
by boredandroid 9y ago
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 provides deduplication within the context of a connect
22.
by boredandroid 9y ago
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 enables correct stream processing on top of Kafka and is arg
23.
by boredandroid 9y ago
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 state/output in Kafka. The trick you described where y
24.
by boredandroid 9y ago
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 consuming messages, no. However, Kafka's design
25.
Build Services on a Backbone of Events(confluent.io)
6 points by boredandroid 9y ago|0 comments
26.
Updating Materialized Views and Caches Using Kafka(theza.ch)
3 points by boredandroid 10y ago|0 comments
27.
Exactly-Once Delivery and Transactional Messaging in Apache Kafka(cwiki.apache.org)
3 points by boredandroid 10y ago|0 comments
28.
by boredandroid 10y ago
I'm one of the original Kafka creators and am an evil corporate shill at Confluent :-) That was a super silly discussion and I'd be annoyed reading it too. It does not, however, represent any kind of "move away from open sour
29.
by boredandroid 10y ago
We haven't broken with ZK, it just isn't part of the protocol clients use anymore. This is important for three reasons: 1. To make clients easy to build 2. To have a single security layer for everything (so you don't have to
30.
by boredandroid 10y ago
This article is pretty out of date, I think the central concerns have actually been addressed. It's true that when we were working at LinkedIn Kafka tended to have much better Java support. Since founding Confluent (I'm one of the

More ›