hands up for having it! Maybe anyone else?
Best,
Kiryl
From: Christophe Bornet
Date: Wednesday, November 1, 2023 at 10:33 PM
To: dev@pulsar.apache.org
Subject: Re: Question about Pulsar gRPC client(s)
Le mer. 1 nov. 2023 à 05:16, Kiryl Valkovich
a écrit :
>
> * So I think we could n
ns
(simpler to deal with, usable with simple CLI tools, browsers,
etc...). So I'm pretty sure we need at least an HTTP+JSON interface.
As you say, it could be brought by the gRPC gateway but that's an
additional component to deploy and it cannot be embedded in the broker
as it's writte
t it for any other
language anymore.
Best,
Kiryl
From: Christophe Bornet
Date: Wednesday, November 1, 2023 at 12:43 AM
To: dev@pulsar.apache.org
Subject: Re: Question about Pulsar gRPC client(s)
Hi Kiryl,
Thanks for mentioning pulsar-grpc.
Indeed, using gRPC simplifies the implementation of th
I think that Christophe suggested the protocol handler approach like KoP (also
forked as DataStax Starlight for Kafka). Due to the several people on the PMC
contributing to that the performance gains were huge and it nearly as
performant as Pulsar.
Best,
Dave
Sent from my iPhone
> On Oct 31,
It's a protocol handler like https://github.com/streamnative/kop that
supports the Kafka protocol. The protocol handler should not be
maintained in the core repo because there are a few people maintaining
the plugin.
And just like Christophe and Zike said, compared with the native
Pulsar protocol,
Another point is that there are many features implemented on the
client side, including batching, chunking, DLQ, etc. This makes it
hard to replace the existing pulsar clients completely.
Zike Yang
On Wed, Nov 1, 2023 at 4:43 AM Christophe Bornet wrote:
>
> Hi Kiryl,
>
> Thanks for mentioning p
Hi Kiryl,
Thanks for mentioning pulsar-grpc.
Indeed, using gRPC simplifies the implementation of the networking logic
(keep-alive, reconnection, flow control,…). On the other hand, the Java
gRPC implementation makes a lot of buffer copies to cleanly separate the
network and app layers but that tak
Hi! Am I understanding it right, that if this project
https://github.com/cbornet/pulsar-grpc is merged to the apache/pulsar repo, we
could easily cover non-mainstream platforms that are supported by gRPC, but
don't have ready-to-use Pulsar clients?
https://github.com/apache/pulsar/wiki/PIP-59:-
