Often seen on projects with multiple services in mind, many issues arise around communication data. The client's schema is often painstakingly maintained to be up-to-date to the server's to avoid unintended outcomes. Requests that require joint effort from multiple services suffer from latency because the transmission itself takes time. Such problems happen across the board, from personal projects to industry services. However, there is one thing that many players in the industry - like Stripe, Shopee, and Gojek - adopt to deal with this: Protocol Buffers.
Protocol Buffers (frequently known as Protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. Developers define message structures in .proto files using Protobuf's syntax, Protobuf compilers generate structure codes in the language of choice, and application code uses it to be referenced and or (de)serialized. Not just simple, Protobuf is cross-compatible, type-safe, and efficient, making it a great choice not just for the industry, but for all projects.
Round C:
Topic:
Adopt Protocol Buffers to Upgrade Projects with Multiple Services
WIIFY:
Learn the industry approach on a problem you know well.
Stand yourself out on the internship/work search by understanding and adopting this early on in your career.
Get a starting step to even more interesting stack in the industry, like Remote Procedure Calls with gRPC.
Key Points:
Protobuf is a language-neutral data serialization and representation format.
Protobuf is easy to set up and integrate, in just three steps.
Protobuf can be compiled into many languages, making it a choice for cross-compatible schema.
Protobuf is type-safe, so developers need not to worry about payload being in the right format.
Protobuf is efficient, beating JSON at time and space even in its own home, JavaScript.
Impact:
Know: What are Protocol Buffers and its benefits
Believe: Projects can be easily maintainable and efficient with Protocol Buffers
Often seen on projects with multiple services in mind, many issues arise around communication data. The client's schema is often painstakingly maintained to be up-to-date to the server's to avoid unintended outcomes. Requests that require joint effort from multiple services suffer from latency because the transmission itself takes time. Such problems happen across the board, from personal projects to industry services. However, there is one thing that many players in the industry - like Stripe, Shopee, and Gojek - adopt to deal with this: Protocol Buffers.
Protocol Buffers (frequently known as Protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. Developers define message structures in
.protofiles using Protobuf's syntax, Protobuf compilers generate structure codes in the language of choice, and application code uses it to be referenced and or (de)serialized. Not just simple, Protobuf is cross-compatible, type-safe, and efficient, making it a great choice not just for the industry, but for all projects.Round C:
Topic: Adopt Protocol Buffers to Upgrade Projects with Multiple Services
WIIFY:
Key Points:
Impact:
Slides: Round C: https://docs.google.com/presentation/d/1cf0zvhmd-B5AG9d8E0i_JQp4y7d_iqzsj4Ws4xblJMs/edit?usp=sharing
Round B:
Topic: Adopt Protocol Buffers to Upgrade Projects with Multiple Services
WIIFY:
Key Points:
Impact:
Slides: Round B: https://docs.google.com/presentation/d/1IVHTDl72EyG5SWH2A4MevZVoaGEQhFWnF2YVcil0sv0/edit?usp=sharing