Hi,
I've read about Kafka being used for huge paces and volumes of messages. My
scenario is a bit different, I'm looking for mostly only persistence of a
message queue, where the queue is usually not huge.
This scenario means that messages are not typically queued for long.
Why Kafka? What I like
Hey Matan,
At LinkedIn we end up having lots of topics--some are very high volume and
some very very low volume. It works fine for low-volume topics.
At this time we don't support any kind of per-consumer throttling, that
would be a nice thing to have.
-Jay
On Sun, Dec 16, 2012 at 2:23 AM, Mat
Hey guys,
Thanks for passing those along. I fixed them.
If anyone sees any issues with the incubator redirects let me know (they
seem to work for me).
One weird thing is that our KEYS file is still in SVN. Perhaps that should
be moved to the git repo?
Neha--as Johan mentions two of your present
> 7. There hasn't really been much a discussion on Logo, though we definitely
> need one. I offered to act as "personal programming slave" to any of the
> LinkedIn designers if they would make us a nice logo. If that approach
> fails maybe we should just do 99 designs?
>
We're happy to propose one
