We've launched custom lint and breaking change plugins for Buf! Check it out to see how easy it is to author, test, and consume your own lint and breaking change rules via the Bufplugin framework: buf.build/blog/buf-custo…

🌟 Bufstream is the first cloud-native #Kafka implementation verified by Jepsen! 🔥 Read our blog to learn more: buf.build/blog/bufstream… Jepsen offers auditing services for distributed systems, verifying that software performs as promised. We value transparency, so we're sharing

Jepsen: Bufstream 0.1.0 #HackerNews jepsen.io/analyses/bufst…

100GB/s in a Bufstream cluster running active-active across multiple regions? We're looking at the results right now - and we haven't even approached Bufstream's limit. We're excited to share the results with the world in the coming weeks. Follow for updates.

Banger thread by Stanislav Kozlovski about the story and architecture of Bufstream, and how it is not only the cheapest Kafka in the market, but also brings the power of type safety to data streaming workloads. Check it out!

Bufstream: 100 GiB/s of writes and 300 GiB/s of reads at 350ms latency in GCP. For a cost that’s literally 25x lower than the cheapest Confluent Cloud offers. Bufstream’s stateless design gives you all of this, with the operational simplicity that lets you sleep at night.

Can you tell the difference between the end-to-end latencies of a multi-region Bufstream cluster and a single-region one? On the left is the single-region cluster from our last blog post. On the right is a new test we just completed with 100 GiB/s writes replicated through two

Running a 100 GiB/s multi-region Kafka workload would cost you around $100M a year 👀 Except no single cluster would be able to sustain that. Bufstream just did it in ONE cluster, at less than ONE-THIRD the price. How? Surprisingly easy! All due to their simple and extensible

Bufstream: A multi-region, active-active Apache Kafka-compatible cluster tested to 100 GiB/s writes and 300 GiB/s reads. Instant failover. Scales all the way from 0 to 100 GiB/s with no operational toll. 1/3 the cost of an Apache Kafka stretch cluster (which won't even work at

We're starting a weekly series of tips on the Buf blog to highlight things everyone should know about Protobuf. Our first post is live today! Tip #1: Field names are forever

TL;DR: Compression is everywhere: CDNs, HTTP servers, even in RPC frameworks like Connect. This pervasiveness means that wire size tradeoffs matter less than they used to twenty years ago, when Protobuf was designed. buf.build/blog/totw-2-co…

TL;DR: Protobuf’s distributed nature introduces evolution risks that make it hard to fix some types of mistakes. Sometimes the best thing to do is to just let it be. buf.build/blog/totw-4-ac…

Is it time to say that Protobuf won the schema wars?

Don’t miss our interactive workshop on bringing schema-driven governance to Kafka. Our engineering and product teams will deep dive into how it’s done. Plus, we’ll answer your questions throughout. 📷 Thursday, May 29 📷 9 AM PDT / 12 PM EDT / 5 PM BST buf.build/events/worksho…

TL;DR Don’t use required, no matter how tempting. You won’t be able to get rid of it later when you realize it was a bad idea. buf.build/blog/totw-8-ne…

TL;DR: The first 15 field numbers are special: most runtimes will decode them much faster than the other field numbers. When designing a message type for decoding performance, it’s good to use these field numbers on fields that are almost always present. buf.build/blog/totw-9-so…

Announcing hyperpb, a fully-dynamic Protobuf parser that achieves 3x performance over generated Go code! Our hyperspeed dynamic parsing turns once-unscalable products into ordinary, even essential components of your stack. Check out our benchmarks! ⚡ buf.build/blog/hyperpb

LinkedIn gave us Kafka, but left 3 issues: Schema evolution, plug-and-play integration & governance. We solved all 3: ✅ Buf CLI breaking change detection ✅ Bufstream's broker-side schema awareness ✅ BSR team-wide governance Let’s finish what Kafka started 🚀

🎉 Protovalidate hits v1.0! It’s a big milestone for the Protobuf semantic validation library trusted by Microsoft, GitLab, Nike and thousands more to: ✅ Define validation rules only once ✅ Enforce everywhere (Go, Java, Python, C++, TypeScript) Details: buf.build/blog/protovali…