[
https://issues.apache.org/jira/browse/KAFKA-14306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618871#comment-17618871
]
maayan shani commented on KAFKA-14306:
--------------------------------------
[~dengziming] Hi, the kafka protocol can coexists with protocol buffer, (over
tcp), the packages of many languages is more then good enough.
you can also managed the bp with backward compatibility and version control to
manage carefully (like the document refer)
> add uniform serializer and deserializer to the kafka protocol
> -------------------------------------------------------------
>
> Key: KAFKA-14306
> URL: https://issues.apache.org/jira/browse/KAFKA-14306
> Project: Kafka
> Issue Type: New Feature
> Components: clients, core, protocol
> Reporter: maayan shani
> Priority: Trivial
>
> recently I noticed every client (java, js, python ...) uses a different
> serializer and deserializer,
> by adding the protocol buffer (.proto) files to the Kafka project, and
> describing the Kafka protocol, all clients and even the brokers can connect
> with more ease.
> there will be less duplication of code,
> it will be easy to add client implementation fast the clients will be more
> reliable and more up-to-date like the official Kafka protocol
>
> * protocol buffer is a uniformed way developed by google to describe
> serializer and deserializer protocols
> related information:
> the protobuf by google -
> https://developers.google.com/protocol-buffers
> for example, pulsar added protobuf files to the project
> pulsar protocol buffer -
> [https://github.com/apache/pulsar/blob/master/pulsar-common/src/main/proto/PulsarApi.proto]
> [https://pulsar.apache.org/docs/developing-binary-protocol]
> pulsar node js client -
> [https://github.com/ayeo-flex-org/pulsar-flex]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
