←
Buf393 posts
Buf avatar

Buf

@bufbuild

Modern Protobuf and gRPC

◷ Joined August 2019▧ 21 Photos and videos
marwan avatar
⟳ Buf retweeted
marwan@_marwanad·Oct 26

when are we getting protobuf for agent communication? the amount of unstructured yapping between agents is getting out of hand

Marvin avatar
⟳ Buf retweeted
Marvin@PrakashMarvin·Oct 19

Rebuilding the trading engine in Rust. Today: how to define the types on the data streams. Option A: hand-write them everywhere. Option B: protobuf + Buf, generated at build time. I went with B. Hand-written types drift. Generated ones can't — and so far it's faster.

Buf avatar
Buf@bufbuild·Oct 7

connect-go v2 is here. We took four years of production experience and redesigned the API: simpler method signatures (no more generic Request/Response wrappers), pluggable transports, a unified interceptor model, and a migration tool to automate the upgrade. Learn more: buf.build/blog/connect-go-v2

Buf avatar
Buf@bufbuild·Sep 30

We've all seen countless "gRPC vs REST" posts filled with advice about how REST is good for public/browser-facing APIs and gRPC is good for internal APIs and services. These discussions often miss the better third option: both. With Connect, you get browser-friendly APIs, a choice of JSON or binary Protobuf, and no binary framing weirdness for unary calls. You keep the schema and generated clients, and browsers can call the same server as your existing gRPC clients. No gateway required. Interested? Try out ConnectRPC and read more in this week's blog post. buf.build/blog/grpc-vs-rest-…

Alexander Belanger avatar
⟳ Buf retweeted
Alexander Belanger@abelanger5·Sep 23

we just migrated our gRPC services to the ConnectRPC protocol instead. this turned out to be a fairly simple migration, but unlocks a whole bunch of new features for Hatchet in the next few months. gRPC is fantastic, but support across runtimes isn't great. in particular, we've had a bunch of requests for serverless runtimes like @Cloudflare Workers which we haven't been able to support because of gRPC compatibility issues. the original serverless runtimes were built around the fetch() API, which is missing a bunch of http/2 features that we need. we've been quietly waiting on gRPC support across these runtimes -- and Cloudflare just rolled it out in beta! -- but demand was high enough that we're just sending it. The great part about ConnectRPC is that it's fully gRPC compatible, so existing clients will still work. Just a 10/10 dev experience overall: connectrpc.com/ full serverless and sandbox support coming soon.

0:13
Buf avatar
Buf@bufbuild·Sep 22

How well do you actually know Protocol Buffers? We put together a quick interactive quiz covering schema design, field rules, and wire format mechanics. protobuf.com/quiz/ The questions are now randomly selected from a question bank so retrying will give you a few new questions. #protobuf #grpc #quiz

Buf avatar
Buf@bufbuild·Sep 17

Protovalidate performance has improved dramatically. 3x faster in Go, 10x faster in Java, 13x faster in TypeScript and 484x faster in Python. No, that wasn't a typo. It really is that much faster than before. buf.build/blog/faster-protov…

Buf avatar
Buf@bufbuild·Sep 8

In case you missed it, here is a roundup of the latest from the Buf blog: - gRPC-Web Failed the Web: buf.build/blog/grpc-web-fail… - connect-rust joins the Connect project: buf.build/blog/connect-rust-… - The modern Protobuf workflow: buf.build/blog/the-modern-pr… - Protobuf-ES just got a lot faster: buf.build/blog/protobuf-es-p… - Protobuf Tip #10: Choosing the right integer type: buf.build/blog/choosing-the-…