Google SWE teaches systems design | EP43: Data Serialization (Protocol Buffers, Thrift, Avro)

แชร์
ฝัง
  • เผยแพร่เมื่อ 11 พ.ย. 2024

ความคิดเห็น • 9

  • @danielvega646
    @danielvega646 4 หลายเดือนก่อน +1

    -"and I'm gonna pass out", the legend said.

  • @datmickey1966
    @datmickey1966 หลายเดือนก่อน +1

    Great video!! The outro is hilarious 😂

  • @sahilgupta6205
    @sahilgupta6205 2 ปีที่แล้ว +1

    Very well explained !! Good Job !! This entire series is very helpful !

  • @higiniofuentes2551
    @higiniofuentes2551 3 หลายเดือนก่อน +1

    Thank you for this very useful video!

  • @raj_kundalia
    @raj_kundalia ปีที่แล้ว +1

    This helps! Thank you!

  • @eudaimonian9473
    @eudaimonian9473 2 ปีที่แล้ว +2

    Gigachad in the house

  • @dibll
    @dibll ปีที่แล้ว +4

    Why do these protocols called Binary? If we take JSON as an example it gets converted into binary(0 and 1s) when transferring over wire or on Disk. The advantage with Protocol Buffer is that we have less data to transfer as there are no field names but it's still text that will get converted to binary(0s and 1s) at the physical layer. I think these is some gap in my understanding of this concept.Could you pls help?

    • @jordanhasnolife5163
      @jordanhasnolife5163  ปีที่แล้ว

      Can you elaborate on this? I'm not quite sure what you're asking

    • @thomasziereis330
      @thomasziereis330 ปีที่แล้ว

      Its not text that gets transfered, for example: sending the number 34578692 takes in string representation as many bytes as there are digits, so in this case 8 byte but this number can also be sent as an 4byte integer. Yes in the end it 0s and 1s either way but you can encode the values differently and not just as strings