Hi Apache Pulsar community, I’m a huge fan of the potential that the pluggable protocol handlers introduced in Pulsar 2.5 unlock for increasing Pulsar popularity by reducing the friction to adopt it. This includes both general-purpose APIs like REST and gRPC, and compatibility layers for other streaming products like Kafka and AMQP.
I’ve created a PIP <https://github.com/apache/pulsar/wiki/PIP-59%3A-gPRC-Protocol-Handler> and an implementation of a gRPC protocol handler, but review of the pull request stalled out <https://github.com/apache/pulsar/pull/6512> so I moved my implementation to my own repository <https://github.com/cbornet/pulsar-grpc> while I finished it. With development and testing effectively complete, I’d like to reopen the discussion: 1. How can I move forward with contributing my gRPC protocol handler to Apache Pulsar? Is this something that is interesting and useful to the broader community? 2. More broadly, what policy do we want to establish for Pulsar protocol handlers and other compatibility layers? As indicated above, I think that we should provide Pulsar with “batteries included” to make it as easy as possible for new users to get started. Best regards. Christophe
