[GitHub] bjustin-ibm commented on issue #183: delegate sendMessage to the provider service

[gi...@git.apache.org]

bjustin-ibm commented on issue #183: delegate sendMessage to the provider service
URL: https://github.com/apache/incubator-openwhisk-package-kafka/issues/183#issuecomment-309748332
 
 
   I assume that the benefit of this is that the total time from when the action is invoked and the message is produced to the Kafka instance is on average lower, by way of not taking the time to establish a Kafka connection every time a message is produced.
   
   Implementing this means that the action must have a reliable communication method to the provider service in order to signal the delegation intent. In order for this to to have the above stated benefit, the time of signaling delegation to the provider service, plus the time to (potentially) re-use an existing Kafka connection to produce a message must be less than the time it takes to produce a message using a new Kafka connection. In the worst case (when the established connection does not yet exist) this is always slower than the current implementation, meaning that the best case should be significantly faster in order to make up the difference.
   
   My gut feeling is that HTTP connection overhead is at least that of establishing a Kafka connection. While redis may (I really don't know...) be faster, I'm not certain that it is 100% reliable for this kind of scenario. While Kafka is reliable, obviously the connection overhead is the same.
   
   @sjfink what do you think?
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services