Each consumer group is a set of one or more machines. The complete stream is load balanced over the machines in a group (e.g. for a group of N machines, each machine gets 1/N of the messages). Each group gets a complete copy of the stream.
So if there is a single consumer group for all consumers this is similar to a traditional queue. If each consumer process has its own group id, then this is similar to traditional pub/sub. Any case in between allows you to provide a sort of pub/sub that is load balanced over a cluster of machines. Does that help? -Jay On Fri, Sep 9, 2011 at 1:40 PM, Chandra R <mybaywo...@gmail.com> wrote: > Hello All, > > I am trying to understand the Kafka 1:N pattern. > I am trying to understand it in terms of a twitter like app. > > For every user there will be 1 Producer. Each follower will be in its own > consumer group and there will be a Broker which will connect Producer to > Consumer groups. > > Am I getting it right ? > > Thanks. Any advice would be appreciated. > > regards > > Chandra R >
