gRPC — Animate | AI Wisdom

← Back to topic
🎞 ANIMATE · Mode 3 of 5 · +100 XP— gRPC
📋Protobuf
⚙️Service Def
🔄Server
✅Client
🎯 Next: Test →
Step 1 / 4
Speed
Protobuf Schema
Protobuf IDL — language-agnostic type definitions💡 Analogy
Like a blueprint that any contractor (any language) can use to build the same structure.
Proto files define message types and services. Field numbers (= 1, = 2) identify fields in the binary encoding — they never change once set.
Console Output
> protoc generates: user_pb.js, user_grpc_pb.js
> Fields encoded as binary — 5-10x smaller than JSON
> Field number 1 = id, 2 = name (stable across versions)
●user.proto
Protobuf SchemaL2–15
1// user.proto — protobuf schema (language-agnostic)
2syntax = "proto3";
3package user;
4 
5message User {
6  string id = 1;
7  string name = 2;
8  string email = 3;
9  repeated string roles = 4;
10}
11 
12message GetUserRequest { string id = 1; }
13message CreateUserRequest {
14  string name = 1;
15  string email = 2;
16}
17 
18service UserService {
19  rpc GetUser(GetUserRequest) returns (User);
20  rpc CreateUser(CreateUserRequest) returns (User);
21  rpc StreamUsers(GetUserRequest) returns (stream User); // server streaming
22}
23 
24// TypeScript gRPC server implementation
25import * as grpc from '@grpc/grpc-js';
26 
27const userServiceImpl = {
28  getUser: async (call: any, callback: any) => {
29    const user = await db.findById(call.request.id);
30    if (!user) {
31      callback({ code: grpc.status.NOT_FOUND, message: 'User not found' });
32      return;
33    }
34    callback(null, user);
35  },
36 
37  streamUsers: (call: any) => {
38    db.findAll().then((users: any[]) => {
39      users.forEach(user => call.write(user));
40      call.end();
41    });
42  },
43};
44 
45declare const db: any;
45 lines
Timeline — 4 Steps
Protobuf Schema
Protobuf IDL — language-agnostic type definitions💡 Analogy
Like a blueprint that any contractor (any language) can use to build the same structure.
Proto files define message types and services. Field numbers (= 1, = 2) identify fields in the binary encoding — they never change once set.
Console Output
> protoc generates: user_pb.js, user_grpc_pb.js
> Fields encoded as binary — 5-10x smaller than JSON
> Field number 1 = id, 2 = name (stable across versions)

Was this page helpful?

Discussion

Protobuf IDL — language-agnostic type definitions

💡 Analogy

Like a blueprint that any contractor (any language) can use to build the same structure.

Proto files define message types and services. Field numbers (= 1, = 2) identify fields in the binary encoding — they never change once set.

Console Output

> protoc generates: user_pb.js, user_grpc_pb.js
> Fields encoded as binary — 5-10x smaller than JSON
> Field number 1 = id, 2 = name (stable across versions)

Protobuf IDL — language-agnostic type definitions

💡 Analogy

Like a blueprint that any contractor (any language) can use to build the same structure.

Proto files define message types and services. Field numbers (= 1, = 2) identify fields in the binary encoding — they never change once set.

Console Output

> protoc generates: user_pb.js, user_grpc_pb.js
> Fields encoded as binary — 5-10x smaller than JSON
> Field number 1 = id, 2 = name (stable across versions)