A proposed simplification of the consumer (see #32 for a discussion of the problem with the current design). It drops the unnecessary queue nor those it force the user to use a thread pool. It is just a shallow Ruby layer over the Kafka high-level consumer. Like it exposes the message streams to the user and allows him to select how many streams he wants. If the user wants the old behavior of all messages multiplexed into a single queue, all they have to do is choose a single stream. The Kafka consumer group example can then be easily reproduced by the user, outside of the library.
joekiller
commented
9 years ago
A proposed simplification of the consumer (see #32 for a discussion of the problem with the current design). It drops the unnecessary queue nor those it force the user to use a thread pool. It is just a shallow Ruby layer over the Kafka high-level consumer. Like it exposes the message streams to the user and allows him to select how many streams he wants. If the user wants the old behavior of all messages multiplexed into a single queue, all they have to do is choose a single stream. The Kafka consumer group example can then be easily reproduced by the user, outside of the library.