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 salutations
M. Lohith Samaga
-----Original Message-----
From: Kuldeep Kamboj [mailto:[email protected]]
Sent: Friday, April 22, 2016 12.08
To: [email protected]
Subject: How to build strategy for particular setup of kafka
I have three applications let named AppA, AppB, AppC. All could have several
some message queue named like
AppA
MsgQueueA
MsgQueueB
AppB
MsgQueueA
MsgQueueB
MsgQueueC
AppC
MsgQueueA
MsgQueueB
MsgQueueD
I have very little exposure for Apache Kafka and even for message queue
concepts.
I just thinking to create topics for MsgQueueA, MsgQueueB and so on. But I am
confused how to integrate AppA, AppB, AppC. Partition and Consumer group look
like wrong choices for them.
Also If separation of queue/topic for Apps is better idea instead of re-using
them for different Apps for better debugging Like below
AppA
AppAMsgQueueA
AppAMsgQueueB
AppB
AppBMsgQueueA
AppBMsgQueueB
AppBMsgQueueC
AppC
AppCMsgQueueA
AppCMsgQueueB
AppCMsgQueueD
--
Kuldeep Kamboj
Information transmitted by this e-mail is proprietary to Mphasis, its
associated companies and/ or its customers and is intended
for use only by the individual or entity to which it is addressed, and may
contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded
to you without proper authority, you are notified that any use or dissemination
of this information in any manner is strictly
prohibited. In such cases, please notify us immediately at
[email protected] and delete this mail from your records.
