Thanks for your responses, Dave...
This is indeed clear and informative!
Hello Miguel and Samson,
Just to add to what Dave just stated and to summarize the use cases a bit:
The Kafka documentation has a good summary here with the APIs that are
provided within the project
https://kafka.apache.org/documentation/#api
To add to what's in the documentation, we have a coup
Yes, Kafka Consumer and Kafka Streams are just libraries. My point with that,
is that it’s not difficult to switch from one to the other as your needs
evolve.
There are several ways that Kafka Streams aids in processing. It provides a
rich set of functions for transforming, filtering, branchin
DaveKlein, in the reply email of "Kafka Streams" on the question to use Kafka
Streams or just a consumer you specified:
> But Streams and Consumer are just libraries, so start with Consumer and if
> you find yourself doing more processing, consider moving to Kafka Streams.
I though Kafka Consum
If you are not doing any transformation or filtering of the data before writing
it to the db, then you’re probably better off with a consumer or Kafka Connect.
Kafka Streams shines when you have processing to do on the data as it is
consumed. Especially if you do any stateful transformations, s
Hi,
I'm looking over your documentation at docs.confluent.io on Kafka Streams,
but I couldn't find the information I'm looking for. What I need to know
are:
1. When should one use Kafka Stream instead of regular Kafka Consumer?
2. If I'm not performing data transformation, but simply reading from
