Asking Jev questions with Protobuf
A protoc plugin that turns Jev questions in a .proto file into typed Go, TypeScript, and Python clients.
A protoc plugin that turns Jev questions in a .proto file into typed Go, TypeScript, and Python clients.
Learn how to generate JSON Schema and OpenAPI specs using Protobuf.
Go, Java, and TypeScript now run Protovalidate's standard rules as native code, while protovalidate-py 2.0 replaces its pure-Python core with a much faster native extension.
Deep dive into a space-saving encoding technique.
A tour of the modern Protobuf workflow, from compatibility and code generation to RPC, validation, and editor tooling, and how each piece builds on the same schema.
Protobuf-ES v2.14 serializes up to 5x faster and parses up to 2x faster, with no API changes and no new build options. Update the package and your code gets faster.
Protobuf has ten integer types. Use int64. In Go, even the slow cases decode a thousand integers in a few microseconds, so the choice almost never matters.
We're announcing protobuf-py, a complete, 100% conformant Protobuf runtime for Python that feels like Python and matches the performance of Google's C engine on real workloads.
Buf is proud to announce the first fully-featured, spec-compliant LSP server for Protobuf. The Language Server Protocol is the standard API for integrating language support into your favorite IDE or text editor, such as VSCode, IntelliJ, or Neovim. An LSP server provides the smarts that power go to definition, code completion, finding references, and semantics-aware syntax highlighting.
After two years of development, we're proud to announce that Protovalidate has reached v1.0. Protovalidate is the semantic validation library for Protobuf. Protobuf gives you the structure of your data, but Protovalidate ensures the quality of your data. Without semantic validation, you're stuck writing the same validation logic over and over again across every service that consumes your messages. With Protovalidate, you define your validation rules once, directly on your schemas, and they're enforced everywhere.