The Ledger
Every statement that passed quotation and attribution checks. Mix any filter with any other: certainty 1/5, debate potential 5/5, or both at once.
why aren't all 11 resolved? a statement only gets an assessment when the public record can support or contradict it. opinions and what-ifs never can, and 0 checkable ones are still open, waiting for their date. predictions held up or didn't; assertions are supported or contradicted. on every card: ▮▮▮▮▮ certainty · ▮▮▮▮▮ debate potential. speakers are clickable
Narkhede: Confluent ignored narrow ICPs to capture the broad Kafka base
“Kafka, you know, that was one of the reasons why we couldn't or we didn't sort of narrowly focus on an ICP like traditional companies do for good reason. It was because, you know, the Kafka adoption base was so broad and for Confluent to quickly convert those …”
Narkhede: Kafka was used by 50% of Fortune 500 when Confluent launched
“Confluent kind of started with a proven technology that was used at, you know, roughly 50% of Fortune 500 companies at that point in time.”
Kreps: Open-Source Projects Require Product Marketing to Drive Adoption
“What was it that it took us probably several years to discover was basically product marketing. You know, in an open source context was, yeah, you gotta tell people why it's interesting.”
Narkhede: Features enabling end users should remain open source
“Features that directly
Enabled the end users of the open source product.
We believe should ideally remain open source or be open source.”
Narkhede: Operational ease is the right starting point for open-source companies
“The first one was operational ease, you know, offering tools and enhancements to simplify the deployment, management, and scaling of Kafka clusters, which is actually, I think, the right starting point for many open source companies.”
Narkhede: Confluent never split engineering teams between cloud and on-prem
“We kept the foundational teams the same. So there was only one team ever working on Apache Kafka and the foundation. There was only one team that was ever developing a specific proprietary feature set. So we never split, you know, specific teams or individual …”
Redpanda improves on Kafka with better developer experience and no ZooKeeper
“They were saying, I'm faster than Kafka, which is what a business wants to hear. Higher efficiency, lower cost, et cetera. And the developer experience is better. There's a single statically linked C++ binary. It's easier to work with it on your laptop, lower …”
Kreps: Apache Kafka Sat on the Shelf During First Open-Source Year
“And you know, it actually took a while, you know, probably the first year, it mostly sat on the shelf as a open source project, which we were quite disappointed about.”
Narkhede: Confluent was founded four years after Kafka was open-sourced
“So this conference started four years after Apache Kafka was open sourced and became successful and
It was very much an organic decision.”
Narkhede: Confluent's initial branding was easy because of Kafka's popularity
“At Confluent, we could lean on the brand of a very popular Open source projects, so the zero to one branding phase was actually really easy. With Ocelor, you're, you know, humbled that you're starting with something that people don't really know about.”
Narkhede: Kafka was built only after finding no existing streaming platforms
“We actually began by researching the market to see if anyone had built something like that. So definitely wasn't the preference to build Apache Kafka, but when we realized that nothing else existed, we decided to take the leap and start Apache Kafka, open sour…”