protobuf schema-validation data-quality cel-expressions rpc-frameworks

Protovalidate reaches v1.0 with production stability

Define validation rules once in your proto schema, enforce them everywhere across Go, Java, Python, C++, and TypeScript—no code generation per language required.

Summary

Eliminates duplicated validation logic across services consuming the same messages. Rules colocated with schemas make data quality constraints impossible to forget or misconfigure.

Why it matters

Eliminates duplicated validation logic across services consuming the same messages. Rules colocated with schemas make data quality constraints impossible to forget or misconfigure.

Implementation verdict

Replaces protoc-gen-validate (PGV) and ad-hoc per-service validators. Requires proto3 adoption and migration from PGV if you're using it. Ready now—production-deployed at Microsoft, F5, GitLab, CoreWeave, Eurostar, ANZ, Bayer, Nike, and Cerbos.

Sources

1.Protovalidate provides standard annotations to validate common rules on messages and fields, as well as the ability to use CEL to write custom rules
2.companies as diverse as Microsoft, F5, GitLab, CoreWeave, Eurostar, ANZ, Bayer, Nike, and Cerbos already trust Protovalidate
3.v1.0 is a commitment that Protovalidate will not break you
4.validating billions of messages daily
5.When validation rules live with your schemas, they're impossible to forget or misconfigure

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs