Buffa

Why it's ranked here

The case rests on unusually broad protocol coverage and thoughtful Rust representations. The project reports full conformance across binary, JSON, and text formats, preserves unknown data, and supports constrained environments. Pre-release API stability and missing service generation temper that strength.

What's good

Borrowed message views can read strings and bytes without allocating. Owned views retain that behavior across asynchronous boundaries. Cached encoded sizes keep serialization linear through deeply nested messages. Typed open enums preserve unknown numeric values, and unknown fields survive decode and re-encode cycles.

Tradeoffs

Buffa remains pre-release, so breaking changes arrive through minor releases. It generates types from schemas rather than offering a general message derive. Service generation is not supported. Proto2 optional fields lack generated getters that apply custom defaults, and constrained builds receive fewer scoped JSON parsing controls.

How to use it well

Choose it for Rust systems that own Protocol Buffer schemas and value editions, wire compatibility, borrowed reads, or constrained runtime support. Use the hosted Buf generator for simple builds, or the build helper when generation belongs in Cargo. Bring separate tooling for RPC service generation.

Observed

License

Apache-2.0

Primary language

Rust

Packaging

Cargo workspace with separately packaged runtime, type, descriptor, codegen, build, YAML, and plugin crates

Install surface

Cargo dependencies for libraries, optional Homebrew plugin binaries, and a hosted Buf remote plugin

Interfaces

Rust libraries, build-time code generation helper, protoc plugin binaries, and Buf remote generation

Platform support

Core runtime supports no_std with alloc; std adds I/O, time conversions, and thread-local JSON options

Validation structure

A dedicated buffa-test workspace crate and separate fuzz build configuration are present