上一篇讲到Protocol Buffers 原理，这一篇主要以iOS平台为例讲解如何在项目中应用。

只编写一份proto定义，就可以自动生成client，自动生成API文档，自动做版本管理的方式你造吗？

In our previous post, we discussed how we utilize FieldMask as a solution when designing our APIs so that consumers can request the data they need when fetched via gRPC. In this blog post we will continue to cover how Netflix Studio Engineering uses FieldMask for mutation operations such as update and remove.

At Netflix, we heavily use gRPC for the purpose of backend to backend communication. When we process a request it is often beneficial to know which fields the caller is interested in and which ones they ignore. Some response fields can be expensive to compute, some fields can require remote calls to other services. Remote calls are never free; they impose extra latency, increase probability of an error, and consume network bandwidth. How can we understand which fields the caller doesn’t need to be supplied in the response, so we can avoid making unnecessary computations and remove calls? With GraphQL this comes out of the box through the use of field selectors. In the JSON:API standard a similar technique is known as Sparse Fieldsets. How can we achieve a similar functionality when designing our gRPC APIs? The solution we use within the Netflix Studio Engineering is protobuf FieldMask.

Protocol buffers and gRPC are established standards for building modern web services. Go modules are now the default way of versioning packages in Go projects. So how can you import and reuse existing .proto definitions from your versioned dependencies while using Go modules?

本文结构总体与 Protobuf 官方文档相似，不少内容也来自官方文档，并在官方文档的基础上添加作者理解的内容。

本文对 ProtoBuf 产生的背景，基本用法，优缺点和使用场景做了概述。

Proto 代码优化实践。

本文要点： netty4+protobuf3多类型传输实现 优雅的实现消息分发 做后台服务经常有这样的流程: 如何优雅的完成这个过程呢？下面分享下基于netty+protobuf的方案: 首先要解决的是如何在netty+protobuf中传输多个protobuf协议

英文原文： Language Guide (proto3) 中文出处： Protobuf语言指南 [译]Protobuf 语法指南 中文出处是proto2的译文，proto3的英文出现后在原来基础上增改了。

Protobuf是Google发布的消息序列化工具。Protobuf定义了消息描述语法（proto语法）和消息编码格式，并且提供了主流语言的代码生成器（protoc）。本文仅讨论Protobuf消息编码格式，并且假定读者已经熟悉Protobuf消息描述语法（proto2或者proto3）。

Google 的 Protocol Buffers 在数据编码的效率上似乎被神化了，一直流传性能是 JSON 等本文格式 5 倍以上，本文通过代码测试来比较具体的性能差别到底是多少。