We are all ready for Current starting tomorrow! Find me and the team at the Responsive booth and learn about all the ways we make your Kafka Streams apps invincible. #current2024

The recording of my #current2024 talk about redefining the limits of Kafka Streams is available to view. The talk shares a blueprint for achieving 99.99%+ uptime with 100k events/s and terabytes of state for your Kafka Streams applications. 👉current.confluent.io/2024-sessions/…

The September edition of #CheckpointChronicle is here! It's packed full of content with links to articles from Responsive, Bill Bejeck, Jack Vanlightly, Uber Engineering, Expedia, GitHub, Airbnb Engineering, and more! 👉 dcbl.link/cc-sep241

How Responsive async processor redefines the scalability limits of Kafka Streams in 20 seconds

The separation of compute and storage is the hallmark of modern systems, and yet both Kafka Streams and Flink embed RocksDB in their compute nodes. This coupling results in severe operational pain, which I believe has held back the adoption of stream processing in general.

Here’s an interesting fact: around 1/3 of the infrastructure cost of running a stateful Kafka Streams app with RocksDB is writing and reading the changelog topic.

Embedding RocksDB in stream processors like Kafka Streams causes a world of operational pain. But that’s not the only reason to drop RocksDB: it was built for local disks and, as Warpstream has shown us, local disks are really expensive in the cloud! 👇🏽 Check out the costs of

Is it end of the road for RocksDB in stream processing? Disaggregated state is the clearly superior architecture, with Responsive investing heavily in SlateDB while Flink 2.0 has forked RocksDB.

Small feature drop, row-level TTL for Kafka Streams: "The ttl function can use either the key or value, or both, to compute the ttl for that row and override the default ttl. It's also possible to .. only expire specific records." docs.responsive.dev/reference/stor…

Some problems are impossible to solve without stream processing: for instance, did you know that Metronome leverages Kafka and Kafka Streams to deliver real time billing features like spend limits at scale? (1/3)

It's said that Silicon Valley is special because the density of smart people leads to chance encounters that don't happen elsewhere. I can attest to that. Here's how a coffee resulted in Responsive building a DB optimized for stream processing in 8 months. (1/n)

Is stream processing interesting because of the new apps it enables, or because it promises better data processing? I'm in the first camp and am proud of the major contributions Responsive has made to the application space. My reflections on what's next responsive.dev/blog/responsiv…

It's remarkable how popular Kafka Streams is. Here's data for people searching for solutions to their Kafka Streams problems and landing on Responsive. That's an up-and-to-the-right chart I love! On that note, what's the best book or blog you've read for optimizing

Kafka Streams had an amazing 2024! Check out Sophie Blee-Goldman's year in review, where she recaps the 25 major improvements the community made to Kafka Streams in 2024! responsive.dev/blog/kafka-str…

This will be the foundation for being able to branch Kafka Streams apps to support seamless blue/green deploys. You can also branch a previous version of the state to debug an issue from the past. Powerful stuff coming to the world of stream processing!

(3/3) Application upgrades were by far the #1 requested topic when we asked what the community would like to learn about earlier this year. We hope you find this helpful! responsive.dev/blog/topology-…

The 2025 blog post series has begun and we're kicking things off with the "official" Kafka Streams upgrade-guide -- check it out for best practices when setting up a new app, rules for safe vs unsafe upgrades, and tips for making the process go smoothly: responsive.dev/blog/topology-…

We are happy to announce that we have completed another SOC2 Type 2 audit along with completing another successful penetration test against our cloud services. You can find the latest reports on our trust center: trust.responsive.dev