Thanks for the feedback Giridhar!
We'll add a comparison with KStreams there as well.
Roughly, the two are similar - The design of Samza certainly influenced
what went
into Kafka Streams. However, here are some key differences:
- Support for non-Kafka source and sink natively: Samza has n
Hi,
Thank you for providing comparison between Samza and Spark Streaming,
Mupd8, Storm.
Looks like there is new player in the field : Kafka Streams (
https://docs.confluent.io/current/streams/index.html).
It will good to have comparison between Samza and Kafka Streams as well.
>From high-le
Hope that helps. Regards!
-Yi
On Wed, Aug 3, 2016 at 11:04 AM, Nick Quinn wrote:
> There has been a lot of talk around town about Confluent's new stream
> processing engine, Kafka Streams. We are currently using Samza and I want
> to get some feedback for myself and other developers
There has been a lot of talk around town about Confluent's new stream
processing engine, Kafka Streams. We are currently using Samza and I want to
get some feedback for myself and other developers on this group list about the
differences and possible advantages to using Samza when compar
On Mon, May 23, 2016 at 10:28 AM, Sriram Ramachandrasekaran <
sri.ram...@gmail.com> wrote:
> Hello Yi, et all,
>
> I've been following Samza and Kafka (and, Kafka Streams). Given the state
> where Kafka Streams is, it provides a nice high level API for consuming
> stu
Sriram,
I had exactly the same questions recently. From what I see, Kafka Streams does
not provide a way for consuming just one partition? Or, at least, it is not an
easy find in the documentation.
This seems to be the major difference between Samza and KStream. I might be
spreading FUD so
Hello Yi, et all,
I've been following Samza and Kafka (and, Kafka Streams). Given the state
where Kafka Streams is, it provides a nice high level API for consuming
stuff from Kafka + support for localized state. If thrown into an
environment like mesos(fronted by marathon), we shoul
