Elias Levy wrote
> Flink:
>
> Pros:
> * Intra-job traffic flows directly between workers.
> * More mature.
> * Higher-level constructs: SQL, CEP, etc.
How is SQL a Pro in Flink? Kafka Streams has KSQL which is at least as good
as Flink's SQL.
--
Sent from:
My 2c:
KStreams:
Pros:
* Streaming as a library: No need to submit your job to a cluster. Easy
to scale up/down the job by adding or removing workers.
* Streaming durability: State is durably stored in Kafka topics in a
streaming fashion. Durability is amortized across the job's lifetime.
* No
This is probably a very subjective question, but nevertheless here are my
reasons for choosing Flink over KStreams or even Spark.
a) KStreams couples you tightly to Kafka, and I personally don't want my
stream processing engine to be married to my message bus. There are other
(even better
