BusySpinWaitStrategy
We need experts comments on this are we going in right direction or instead of WorkerPool we should go ahead with multiple consumers as event handlers which divides the work based on hashing/bucketing or any other mechanism.
Deepak Gupta
--
You received this message because you are subscribed to the Google Groups "Disruptor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lmax-disrupto...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to lmax-disruptor+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Disruptor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lmax-disruptor+unsubscribe@googlegroups.com.
A bit reply to this thread, but can anyone through some light for this use case should we consider Kafka ?
Will it be a wise call to evaluate both the systems ? If we have a highly concurrent system and can afford to lose some of the events what should be choice ? and if we can not afford to lose even one event what should we go ahead with ?