Ryan Worrell

So it was kind of a choice that was forced upon us. There's really no way Kafka has so much momentum behind it that it's pretty much impossible to get broad adoption of something that would be a replacement for it. without having the exact same wire protocol so you can use the exact same clients and stuff like that. It's a lot of work to maintain that compatibility.

So it was kind of a choice that was forced upon us. There's really no way Kafka has so much momentum behind it that it's pretty much impossible to get broad adoption of something that would be a replacement for it. without having the exact same wire protocol so you can use the exact same clients and stuff like that. It's a lot of work to maintain that compatibility.

Thankfully, a lot of that work is front-loaded. It's just you do it once, and Kafka is not a particularly fast-moving open-source project, so they're not changing the protocol every day. Backwards compatibility is very good with Kafka, so thankfully it was mostly a one-time cost, but it's opened up a lot of opportunities because we are compatible

Thankfully, a lot of that work is front-loaded. It's just you do it once, and Kafka is not a particularly fast-moving open-source project, so they're not changing the protocol every day. Backwards compatibility is very good with Kafka, so thankfully it was mostly a one-time cost, but it's opened up a lot of opportunities because we are compatible

To even just doing basic stuff for the company, like being able to do co-marketing with other vendors of products that are compatible with Kafka. If we weren't compatible with Kafka, you know, we would be able to do that. And a lot of the open source tools that we could that we would want to integrate with, like, let's see the.

To even just doing basic stuff for the company, like being able to do co-marketing with other vendors of products that are compatible with Kafka. If we weren't compatible with Kafka, you know, we would be able to do that. And a lot of the open source tools that we could that we would want to integrate with, like, let's see the.

open telemetry collector or vector, these kind of observability agent tools, they all can write data to Kafka and we inherit that benefit right out of the box. So it's been super important for us basically to have that compatibility.

open telemetry collector or vector, these kind of observability agent tools, they all can write data to Kafka and we inherit that benefit right out of the box. So it's been super important for us basically to have that compatibility.

Yeah, so we have a number of large use cases in production today. I can't talk about very many of them, unfortunately, but there are warp stream clusters out in the world processing multiple gigabytes a second of traffic through, and not just like one of them. Like there's a decent number of them at this point. And where we're having success in the market is basically

Yeah, so we have a number of large use cases in production today. I can't talk about very many of them, unfortunately, but there are warp stream clusters out in the world processing multiple gigabytes a second of traffic through, and not just like one of them. Like there's a decent number of them at this point. And where we're having success in the market is basically

The large open source users who are, you know, they feel like the open source product is a bit too challenging for them to run. And there's budget pressure all over the industry today, especially in the, you know, in the corners that we're interested in, like in the observability and security areas. On the analytics side, there's a lot of budget pressure.

The large open source users who are, you know, they feel like the open source product is a bit too challenging for them to run. And there's budget pressure all over the industry today, especially in the, you know, in the corners that we're interested in, like in the observability and security areas. On the analytics side, there's a lot of budget pressure.

So we're a pretty natural fit for those folks who are both tired of running the Opizars project and they're getting budget pressure to decrease their cost. We're having a lot of success there.

So we're a pretty natural fit for those folks who are both tired of running the Opizars project and they're getting budget pressure to decrease their cost. We're having a lot of success there.

Yeah, so I think that for Greenfield projects, there's two different branches of those. There's Greenfield products that are only Greenfield in the sense that they're trying to adopt Kafka for some goal. They're not Greenfield like the application didn't exist before. There's that aspect of it where they're just new users of Kafka.

Yeah, so I think that for Greenfield projects, there's two different branches of those. There's Greenfield products that are only Greenfield in the sense that they're trying to adopt Kafka for some goal. They're not Greenfield like the application didn't exist before. There's that aspect of it where they're just new users of Kafka.

And then there are truly Greenfield projects where the project itself is new and also the choice to choose Kafka is new. And usually those products don't have a super high volume of data. It's the existing initiatives or applications within a company that process a lot of data but are not using Kafka for cost reasons where we are having more success.

And then there are truly Greenfield projects where the project itself is new and also the choice to choose Kafka is new. And usually those products don't have a super high volume of data. It's the existing initiatives or applications within a company that process a lot of data but are not using Kafka for cost reasons where we are having more success.

There's a product that I would love to talk about that won't quite be public by the time this episode is posted, but they're in that first category where it's a large existing product. workload, but they were not using Kafka for a bunch of different reasons, cost being one of them.

There's a product that I would love to talk about that won't quite be public by the time this episode is posted, but they're in that first category where it's a large existing product. workload, but they were not using Kafka for a bunch of different reasons, cost being one of them.