Here are use cases for contrast, if you haven't seen them. https://kafka.apache.org/documentation.html#uses
Also, the most significant operational difference versus traditional message queue brokers is that responsibility for management of where you are in the queue lies on the client side. This has operational impact. So I'd say that if your throughput requirements can be handled by a traditional message broker, you might want to consider them, due to operational complexity issues. Others on this thread may have a more experienced opinion on that than me though. -Suren On Mon, Dec 16, 2013 at 3:31 AM, Guozhang Wang <[email protected]> wrote: > That is quite a general question, which I think grant me to give a general > answer :) > > Kafka is a messaging system designed for high-throughput, so if your use > cases are beyond delivering data it may not be a good fit for you. > > Guozhang > > On Sun, Dec 15, 2013 at 11:57 PM, Menka <[email protected]> wrote: > > > Do we know particular use cases or scenarios where Kafka shouldn't be use > > and why? > > > > Please share. > > Thanks, > > Menka > > > > > > -- > > Blog: http://menkag.blogspot.com > > Facebook: http://www.facebook.com/MenkasJewelry > > > > "Don't let what you cannot do interfere with what you can do" - by John > > Wooden > > > > > > -- > -- Guozhang > -- ___________________________________________ Available at these partners: [image: CloudFlare | shopify | Bigcommerce] SUREN HIRAMAN, VP TECHNOLOGY SOCIOCAST Simple. Powerful. Predictions. 96 SPRING STREET, 7TH FLOOR NEW YORK, NY 10012 O: (917) 525-2466 ext. 105 F: 646.349.4063 E: [email protected] W: www.sociocast.com Increase Conversion Rates up to 500%. Go to www.sociocast.com and enter your URL for a free trial!
