Book Image

Protocol Buffers Handbook

By : Clément Jean
Book Image

Protocol Buffers Handbook

By: Clément Jean

Overview of this book

Explore how Protocol Buffers (Protobuf) serialize structured data and provides a language-neutral, platform-neutral, and extensible solution. With this guide to mastering Protobuf, you'll build your skills to effectively serialize, transmit, and manage data across diverse platforms and languages. This book will help you enter the world of Protocol Buffers by unraveling the intricate nuances of Protobuf syntax and showing you how to define complex data structures. As you progress, you’ll learn schema evolution, ensuring seamless compatibility as your projects evolve. The book also covers advanced topics such as custom options and plugins, allowing you to tailor validation processes to your specific requirements. You’ll understand how to automate project builds using cutting-edge tools such as Buf and Bazel, streamlining your development workflow. With hands-on projects in Go and Python programming, you’ll learn how to practically apply Protobuf concepts. Later chapters will show you how to integrate data interchange capabilities across different programming languages, enabling efficient collaboration and system interoperability. By the end of this book, you’ll have a solid understanding of Protobuf internals, enabling you to discern when and how to use and redefine your approach to data serialization.
Table of Contents (13 chapters)

Building manually with protoc – a summary

As we saw in Chapter 4, we can build proto files with protoc. On top of that, protoc is also a convenient tool for learning about the Protobuf internals because we can use --encode and --decode flags. However, as with every tool out there, protoc has some limitations.

The main limitation comes when the project starts to have a lot of proto files. Let’s say that you have 50 proto files you want to generate C++ code from. You will need to write a command that looks like the following:

$ protoc --cpp_out=. schema1.proto schema2.proto ... schema50.proto

You basically have to type every single file you want to generate code from and the corresponding output location with options. This means that you will have to write a huge command. And, obviously, nobody wants to do that manually.

That is why we have build tools that automatically do that for us. Let’s talk about the different tools available, starting with Makefiles...