Тёмный

Protocol Buffers vs JSON: Efficient Data Serialization Explained 

The Coding Gopher
Подписаться 404
Просмотров 772
50% 1

Опубликовано:

 

25 окт 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 10   
@Technoassassin11022
@Technoassassin11022 4 дня назад
This man is too good! I appreciate the thoroughness and clarity of the explanation. Absolute gem of a channel!
@TheCodingGopher
@TheCodingGopher 4 дня назад
I appreciate the kind words!
@ThingsUploadedbyMe33
@ThingsUploadedbyMe33 4 дня назад
Thanks
@TheCodingGopher
@TheCodingGopher 4 дня назад
No problem :)
@TheCodingGopher
@TheCodingGopher 4 дня назад
I'm going to make a follow-up video showing the end-to-end process of writing a .proto file, generating server and client stubs, implementing request-response logic in a gRPC server, and testing communication between client and server (likely in Go)
@SRG-Learn-Code
@SRG-Learn-Code 4 дня назад
is it easy enough to be implemented regardless of bandwidth necessities? Then can we expect to be using it everywhere in the future?
@TheCodingGopher
@TheCodingGopher 4 дня назад
Yes; protobufs are super easy to implement across different languages. They use less bandwidth due to their compact binary format (compared to text-based for JSON/XML). I would definitely expect to see them everywhere in the future.
@SRG-Learn-Code
@SRG-Learn-Code 4 дня назад
@@TheCodingGopher I wonder if type safety could be achieved by sharing those proto files in server and client. Do you know any framework that do protobufs without libraries right now?
@TheCodingGopher
@TheCodingGopher 4 дня назад
@@SRG-Learn-Code Yes; sharing .proto files between server and client ensures type safety. Most frameworks (e.g. gRPC) still need libraries to handle protobufs, manually encoding/decoding without libraries is possible - it's quite impractical though.
@SRG-Learn-Code
@SRG-Learn-Code 3 дня назад
@@TheCodingGopher Jsdocs autogeneration of proto files is the goal