[{"data":1,"prerenderedAt":22},["ShallowReactive",2],{"tag-list-en-protobuf":3},[4,15],{"title":5,"description":6,"tags":7,"path":12,"date":13,"img":14},"Protobuf FieldMask for Writes: One Update Endpoint, No Ambiguity","A single Update method that changes only the fields you name, with no endpoint per field and no clobbering the rest. How the update_mask brings clean PATCH semantics to gRPC: setting, clearing, nested paths, and the empty-mask trap that can silently wipe data.",[8,9,10,11],"gRPC","Protobuf","API-Design","Mutations","\u002Fbackend\u002Fapi-design\u002Fprotobuf-fieldmask-mutations","2026-07-07",null,{"title":16,"description":17,"tags":18,"path":20,"date":21,"img":14},"Protobuf FieldMask: Let Your API Clients Ask for Only What They Need","One endpoint, many callers, some very expensive fields. Protobuf FieldMask lets each client declare exactly which fields it wants, so your server can skip the costly database queries, remote calls and payload it doesn't need. The idea, a classic example, and the traps.",[8,9,10,19],"Performance","\u002Fbackend\u002Fapi-design\u002Fprotobuf-fieldmask","2026-07-03",1783585187929]