t; well as high availability.
>>
>> Best regards / Mit freundlichen Grüßen / Sincères salutations
>> M. Lohith Samaga
>>
>>
>> -Original Message-
>> From: Gaurav Agarwal [mailto:gaurav130...@gmail.com]
>> Sent: Friday, April 22, 2016 12.44
&g
0...@gmail.com]
> Sent: Friday, April 22, 2016 12.44
> To: users@kafka.apache.org
> Subject: Re: How to build strategy for particular setup of kafka
>
> Hi
> You can have one or two instances of Kafka but you can have one or two
> Kafka topic dedicated to each applicati
April 22, 2016 12.44
> To: users@kafka.apache.org
> Subject: Re: How to build strategy for particular setup of kafka
>
> Hi
> You can have one or two instances of Kafka but you can have one or two
> Kafka topic dedicated to each application according to the need. Partition
> will
12.44
To: users@kafka.apache.org
Subject: Re: How to build strategy for particular setup of kafka
Hi
You can have one or two instances of Kafka but you can have one or two Kafka
topic dedicated to each application according to the need. Partition will have
u in increasing the throughput and
Hi
You can have one or two instances of Kafka but you can have one or two
Kafka topic dedicated to each application according to the need. Partition
will have u in increasing the throughput and consumer group id can help u
to make queue as topic or queue.
On Apr 22, 2016 12:37 PM, "Kuldeep Kamboj"
Thanks for reply,
I understand the your point, But my whole strategy depend on first issue
and that is how I can integrate Apps in architecture. Partition / Consumer
groups have different purpose. If I need to setup three kafka instances
each for App ?
On Fri, Apr 22, 2016 at 12:30 PM, Lohith Sam
Hi,
It is better NOT to share topics among applications. You may have a
wrapper application reading from the queue/topic and routing it to the correct
application, but it is simpler for each application to read from its own topic.
Best regards / Mit freundlichen Grüßen / Sincères salutat
