Jonathan
On Sat, Jun 8, 2013 at 2:09 AM, Jonathan Hodges wrote:
> Thanks so much for your replies. This has been a great help understanding
> Rabbit better with having very little experience with it. I have a few
> follow up comments below.
Happy to help!
I'm afraid I don't follow your argume
On Sat, Jun 8, 2013 at 2:09 AM, Jonathan Hodges wrote:
> Thanks so much for your replies. This has been a great help understanding
> Rabbit better with having very little experience with it. I have a few
> follow up comments below.
Happy to help!
I'm afraid I don't follow your arguments below.
Jonathan
I am aware of the difference between sequential writes and other kinds
of writes ;p)
AFAIK the Kafka docs describe a sort of platonic alternative system,
eg "normally people do this.. Kafka does that..". This is a good way
to explain design decisions. However, I think you may be assumi
A few more details for those following this:
On Sat, Jun 8, 2013 at 9:09 PM, Alexis Richardson
wrote:
> Jonathan
>
> I am aware of the difference between sequential writes and other kinds
> of writes ;p)
>
> AFAIK the Kafka docs describe a sort of platonic alternative system,
> eg "normally peopl
One more useful link...
http://hg.rabbitmq.com/rabbitmq-server/file/bc2fda987fe8/src/rabbit_queue_index.erl#l32
On Jun 8, 2013 9:20 PM, "Alexis Richardson"
wrote:
> A few more details for those following this:
>
> On Sat, Jun 8, 2013 at 9:09 PM, Alexis Richardson
> wrote:
> > Jonathan
> >
> > I
I am not making any assumptions other than Rabbit needs to maintain the
state of the consumers. As the Kafka docs point out this is the
fundamental difference between most providers in the space and Kafka.
Thinking of a high throughput stream of messages and many active consumers
of different spe
