Example convo. 😊 Me: how will you pull data from Kafka to Elastic? Non-kafka: we're going to us a consumer
Me: Ok, is that a standalone app? Non-kafka: no, we're just going to stream it through Kafka and use there out of the box solution Me: Do you need me to configure connect? Non-kafka: Well, we'll need to connect. We're just going to subscribe to the stream. Me: How are you going to subscribe to the stream? Non-kafka: with the out of the box connector Me: OK?!? Do you need me to configure a Connect cluster? Non-kafka: Not at the moment. We're just going to stream the data to our consumer into elastic. Me (hoping to get past the connect issue): Will you actually be using Kafka Streams? Non-kafka: yes, we have to stream data through Kafka Me: Who IS on first? No, I don't think the names are descriptive. 😊 Jonathan Goings -----Original Message----- From: Liam Clarke-Hutchinson <liam.cla...@adscale.co.nz> Sent: Tuesday, October 20, 2020 3:47 PM To: users@kafka.apache.org Subject: Re: Kafka Naming ************************************************ CAUTION: External email. Do not open attachments or click links. Forward suspicious emails to Anti-Spam. ************************************************ Hi Jonathon, Kafka Connect is designed to, well, connect things to Kafka. Kafka Streams is for stream processing using Kafka. They're rather descriptive and apt names, don't you think? If it helps, we abbreviate Connect as KC and Streams as KStreams in our organisation. Kind regards, Liam Clarke On Wed, Oct 21, 2020 at 3:18 AM Jonathan Goings <jgoi...@jackhenry.com> wrote: > I've been working through product redesign and development with > product groups in our organization. > > Has anyone ever tried to explain data flow through Kafka to non-Kafka > people and notice the inconveniently named Kafka product offerings? > > Please rename Connect and Streams. > > Jonathan Goings > > NOTICE: This electronic mail message and any files transmitted with it > are intended exclusively for the individual or entity to which it is > addressed. The message, together with any attachment, may contain > confidential and/or privileged information. > Any unauthorized review, use, printing, saving, copying, disclosure or > distribution is strictly prohibited. If you have received this message > in error, please immediately advise the sender by reply email and > delete all copies. > NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
