Denovo1998 opened a new pull request, #8:
URL: https://github.com/apache/pulsar-java-contrib/pull/8
<!--
### Contribution Checklist
- PR title format should be *[type][component] summary*. For details, see
*[Guideline - Pulsar PR Naming
Convention](https://pulsar.apache.org/contribute/develop-semantic-title/)*.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Each pull request should address only one issue, not mix up code from
multiple issues.
- Each commit in the pull request has a meaningful commit message
- Once all items of the checklist are addressed, remove the above text and
this checklist, leaving only the filled out template below.
-->
<!-- Either this PR fixes an issue, -->
<!-- If the PR belongs to a PIP, please add the PIP link here -->
### Motivation
As we known，Pulsar's current asynchronous publish-subscribe model serves
well for decoupled message distribution, but it lacks a native mechanism for
handling synchronous interactions typical of Remote Procedure Calls (RPC).
This request-reply model can greatly enhance the utility of Pulsar. We can
then use Pulsar as a distributed RPC Framework. This also improves the fault
tolerance of RPC calls.
PIP-371 is also committed to building such a model.
https://github.com/apache/pulsar/pull/23143
https://github.com/apache/pulsar/pull/23194
But we need to implement this distributed RPC framework in a way that does
not intrude into the pulsar core library. Therefore, we need to use two topics,
one is the request topic and the other is the reply topic. The client side
sends RPC requests to the request topic, the server side receives request
message and performs customized processing, and finally sends them to the reply
topic. The client receives the reply message and returns.
### Modifications
<!-- Describe the modifications you've done. -->
### Verifying this change
- [ ] Make sure that the change passes the CI checks.
*(Please pick either of the following options)*
This change is a trivial rework / code cleanup without any test coverage.
*(or)*
This change is already covered by existing tests, such as *(please describe
tests)*.
*(or)*
This change added tests and can be verified as follows:
*(example:)*
- *Added integration tests for end-to-end deployment with large payloads
(10MB)*
- *Extended integration test for recovery after broker failure*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
