Thank you for your feedback, Lari. This has benefitted me a lot.
Although this proposal was not supported, I didn't feel uncomfortable.
Writing code is my favourite thing to do, and participating in the Pulsar
community will also make me very happy.
This weekend, I simply wrote the implementation
On 2024/08/18 13:16:39 SiNan Liu wrote:
> Although at present, there is no support from many people in the email
> discussion. But I think things still have to have a result.
I have provided some feedback to you in my previous messages,
https://lists.apache.org/thread/moc1lnl7mnz1x17o075zywovooko
PIP-371 documentation: https://github.com/apache/pulsar/pull/23143
PIP-371 implementation code: https://github.com/apache/pulsar/pull/23194
This is a native implementation of the request-reply model in pulsar.
Although at present, there is no support from many people in the email
discussion. B
> We all love good performance, however that might not be the most
important matter in all cases. "Such a call would have a long link and lose
performance." Have you measured the performance of the existing solution?
What is your target performance?
> I understand that it's possible to optimize the
On 2024/08/09 01:10:11 SiNan Liu wrote:
> Thank you for your comments.
>
> I took a look at this. There are a few questions.
>
> 1. Compared with my proposal to directly add new functions in
> pulsar-client, the implementation in this repo is through two topics, one
> request topic and one reply
+1 to this if can be natively supported in pulsar(across programming
languages). Its a useful capability in messaging.
https://www.enterpriseintegrationpatterns.com/patterns/messaging/RequestReply.html
On Fri, 9 Aug 2024 at 9:05 AM, SiNan Liu wrote:
> The focus is not on RPC, but on the Reques
The focus is not on RPC, but on the Request-Reply synchronous call model.
This is a relatively simple function enhancement.
As mentioned in the second article above. For the same topic, each message
can be sent synchronously or asynchronously. That is to say, the request
can be initiated synchrono
Thank you for your comments.
I took a look at this. There are a few questions.
1. Compared with my proposal to directly add new functions in
pulsar-client, the implementation in this repo is through two topics, one
request topic and one reply topic. The producer sends the message to the
request t
Thanks for the proposal!
Instead of modifying the existing Pulsar client library, I think it's better to
create a separate library. The request-reply / rpc model can be implemented on
top of the Pulsar client instead of making the support for request-reply a
first class citizen of the client AP
Hi all.
I drafted a proposal to support for request-reply model that implements RPC
calls in pulsar.
https://github.com/apache/pulsar/pull/23143
I'm looking forward to hearing from you.
Thanks,
sinan
10 matches
Mail list logo
