Confluent, every mention
31 scenes, the whole family · ← back to Confluent
tap a year for its mentions
every year anyone Neha Narkhede 41Brett Berson 24Jay Kreps 15
Verbatim, from the transcripts: the passages where Confluent comes up
How to build a company when you’re not an optimist | Jay Kreps (Co-founder and CEO, Confluent)
- ▶ 0:03 Brett Berson He's the co-founder and CEO of Confluent, the data streaming platform built around Apache Kafka, the open source system he and his co-founders created while they were working as engineers at LinkedIn. 4 times in the scene
- ▶ 4:38 Brett Berson For all of the different disciplines, as the business begins to scale, did you think about what is correct in the context of Confluent?
- ▶ 7:56 Jay Kreps The way Confluent came about, there was a open source project. 3 times in the scene
- ▶ 9:25 Brett Berson Maybe just so we have a little bit more scaffolding, you can give us the trailer version of the Confluent story going all the way back to when you were at LinkedIn, and then we'll use that as sort of a jumping off point.
- ▶ 14:47 Jay Kreps You know, is, uh, you know, it was originally just me who worked on this and we added pretty quickly some other really strong engineers, two of whom, uh, became my co-founders at Confluent, Jun and Neha.
- ▶ 20:19 Jay Kreps It's interesting in this area that Confluent operates in, which is, you know, there's kind of very technical, uh, software products, you know, it is often the case that when you see early companies that have quick success, I would say one… 3 times in the scene
- ▶ 38:45 Jay Kreps And, you know, we did start that pretty early in the life of the company. 5 times in the scene
- ▶ 46:43 Jay Kreps There's always two lenses in a company. 3 times in the scene
- ▶ 58:39 Brett Berson Are there, are there things that you were doggedly pursuing in the context of confluent and then you eventually did wave the white flag or whatever the expression would be? 2 times in the scene
- ▶ 1:07:22 Brett Berson Like, there are many things you mentioned that are correct in the context of the vessel that is Confluent, but I'm curious, like, where do you have conviction that these few ideas are broadly correct and maybe underappreciated or…
Winning with open and closed source products | Neha Narkhede (Co-founder at Confluent and Oscilar)
- ▶ 1:22 Brett Berson She's also the co-founder of Confluent, a cloud-native data streaming platform founded by the creators of Kafka. 3 times in the scene
- ▶ 2:20 Brett Berson Maybe we could start by actually talking about the Kafka story and how that kind of got off the ground when you were at LinkedIn, and then we'll use that to sort of talk about sort of the insight for Confluent. 2 times in the scene
- ▶ 5:16 Neha Narkhede So this, uh, conference started four years after Apache Kafka was open sourced and became successful and
- ▶ 11:13 Neha Narkhede Yeah, I think the inception of Confluent is pretty unique, you know, especially when it, when compared to a typical journey of many startups. 6 times in the scene
- ▶ 14:08 Brett Berson I'd love to hear more detail around how you figured out where you would start to build and for what type of customer and what type of use cases to build sort of the first version that ultimately became Confluent. 3 times in the scene
- ▶ 16:19 Neha Narkhede Confluent, you know, in the, in those days, many enterprises were still on premises, and so we had to offer a software product, and later on we complemented it with a SaaS offering. 5 times in the scene
- ▶ 20:17 Neha Narkhede I think the hardest thing was establishing Confluent as an enterprise company. 6 times in the scene
- ▶ 23:50 Brett Berson So for confluent in that first year or two, what was the narrative that you were communicating to customers in the market more broadly? 4 times in the scene
- ▶ 27:19 unnamed speaker So it made sense for all three of us to work together and all three of us to kind of come together and start Confluence. 2 times in the scene
- ▶ 32:58 Neha Narkhede The first is, uh, we built with monetization in mind from the very early days of Confluent.
- ▶ 35:18 Brett Berson How far into Confluent's journey? 3 times in the scene
- ▶ 35:33 Neha Narkhede So in order to sort of remain the, you know, leading technology and leading product in the space, it was very essential that Confluent Cloud, which is a SaaS product, be developed.
- ▶ 40:03 Neha Narkhede Um, the first few, you know, in, in general for Confluent, first many years, it was completely inbound in the sense that Kafka users knew that we were the Kafka company, and they started reaching into Confluent. 6 times in the scene
- ▶ 43:40 unnamed speaker When you zoom out a little bit and you think about those first five years of building Confluent, what were the tough calls or the difficult moments that ended up being correct? 3 times in the scene
- ▶ 53:21 Neha Narkhede Uh, we already had a couple of customers who were interested in using the SaaS offering so that the rest of the goat market, we always focused on the existing Kafka user base and the existing Confluent user base. 2 times in the scene
- ▶ 56:52 Neha Narkhede The third is, you know, having, having had Confluent become a success, um, ambitious that, you know, any next problem I pick should address a big enough problem and should have a big market to go after.
- ▶ 59:40 Neha Narkhede Just like Confluent did in the power of a long-term vision. 6 times in the scene
- ▶ 1:03:35 Neha Narkhede I had experience observing how the most technical companies, which were Khantun customers, still struggling with it, and reflecting on the fact that I also had experience from LinkedIn, observing how LinkedIn had built their systems,…
- ▶ 1:09:05 Neha Narkhede That was not very obvious at Confluent, actually.
- ▶ 1:10:36 Neha Narkhede I don't think that anyone specific comes to mind, but what I've, um, done pretty frequently at Confluent is realize that 3 times in the scene
- ▶ 1:14:00 Neha Narkhede Consumption based business models, um, before, you know, or while building Confluent Cloud.