Nicely done.

You've seen how a .proto file defines a contract, how it becomes generated code and wire bytes, and how descriptors let you build tooling on top.

Where to go next

There is a lot more to Protobuf than this guide covers. These are good places to start.

The full grammar for .proto files, from declarations and field types to options and reserved names.

One binary that compiles, lints, formats, generates code, and catches breaking changes before they ship.

Publish schemas as versioned modules instead of vendoring .proto files, and depend on them from buf.yaml, with hosted docs and generated SDKs.

An RPC framework for gRPC-compatible APIs that also work natively in the browser and on mobile.

Explore Protobuf libraries, runtimes, plugins, and tools from across the community.

Apply the concepts by fixing broken schemas in the interactive exercises.

This whole guide as one PDF, with the reference tables, the exercises, and the quiz bank as appendices.