You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/06/06 07:08:01 UTC
[GitHub] [pulsar] lhotari commented on pull request #15942: [feature][broker] Support HTTP endpoint consume messages
lhotari commented on PR #15942:
URL: https://github.com/apache/pulsar/pull/15942#issuecomment-1147120969
One reason for not adding this to Pulsar Brokers is that it will break Pulsar load balancing. @joefk Did a good write-up about this in https://lists.apache.org/thread/b7yjwn7cycp0r45mop4onfrr4mmp2tbd .
Quoting @joefk 's email:
> First, broker throughput and performance becomes unpredictable. The
current Pulsar load model (and it is used in the load manager for load
balancing) becomes unusable. Not only that, there will be no pre-computed
model that can be used in the load manager. Since the producer and
consumer randomly decide on what is the business logic,and the computation
can change based on the data, the model itself becomes dynamic and the
load manager has to rebuild the model anytime an user updates the business
logic. That is a tall order, worth years of work to implement.
The context was slightly different in that discussion, but I believe that it could be applied to this case too. We shouldn't be adding more business logic to brokers such as HTTP endpoint for consuming message. That could be implemented in a separate component which isn't part of the broker.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org