Is there a best practice on how to handle producer objects for long running 
apps?

Right now I have an app that is long running and will sit for large stretches 
of time (days/weeks) with next to none load and then get slammed. In that case 
I'd like to cache the producer so I don't incur  a hit in creating a producer 
connection. Is it a problem to keep that producer cached? Or should I create a 
new producer every batch of messages I send?

Thanks,
Karl

Reply via email to