Processing Streaming Data with KSQL - Tim Berglund

Apache Kafka is a de facto standard streaming data processing platform, being widely deployed as a messaging system, and having a robust data integration framework (Kafka Connect) and stream processing API (Kafka Streams) to meet the needs that common attend real-time message processing. But there’s more!
Kafka now offers KSQL, a declarative, SQL-like stream processing language that lets you define powerful stream-processing applications easily. What once took some moderately sophisticated Java code can now be done at the command line with a familiar and eminently approachable syntax. Come to this talk for an overview of KSQL with live coding on live streaming data.

[@estebanduvanzzDelgado]

I've been watching videos about stream processing in Kafka for weeks now! and Tim let me tell you is the first speaker whom I was able to understand perfectly to the point of giving me some good inspiration about cool projects in Kafka for my company.
Tim, if you ever read this comment, be sure that you inspired someone's professional life to the top. Keep it up and thank you

[@thexs1118]

This guy is a great speaker

[@ralphbms]

One of the Best presentation on Kafka and Kafka streams !! Awesome 👏 .. Thanks 😊

[@ilmatankeliaviciene2340]

Great presentation ! Thanks Tim !

[@balanepalaiyathane9714]

Great talk/presentation simple powerful and realistic

[@payamysf]

Thanks, very helpful.

[@VaibhavPatil-rx7pc]

Talented speaker!!

[@sapientum8]

That presentation is just kafkaesque.

[@NaveenSiddareddy]

38:28 is where i see the value.. storage - i/o cost is fine but syncing is where the value is ?

[@tomknud]

Would the data 'of' a select be from the beginning of time or from the time you hit return?

[@leofonseca8144]

Is the Kafka retention policy the only approach to trimming what otherwise seems like a very quickly growing volume of immutable datasets... sorry messages, assuming KSQL doesn't have a DELETE FROM STREAM ... retention policy seems like a very blunt approach. Is there a reference to best practises for managing data retention in a Kafka environment?

[@rkravinderkumar05]

what will be the retention period for ksql tables? Can it be stored permanently?

[@NaveenSiddareddy]

12:55 Tim mentions 2 important differences with legacy queuing , one is storing the message, whats the other?

[@zisispontikas2038]

The other is that you can have more than one type of consumer reading the same message. A logging consumer and an aggregating consumer for example

[@AnuragVishwa]

Even you can replicate the data from kafka queue to your database in case of failure, since the messages in kafaka queue are immutable, so based on the timestamp you can perform manipulations.

[@DevWonYoung]

AWESOMEEEEEE!!!

[@pavelbaranov6635]

Thought you work for Datastax ...

[@BryanChance]

kSQL is awesome...

[@calofiremil7863]

This dude is a Rich Hickey fan

[@cafeliu5401]

The partition problem is a very big pain that you have to consider every move down the road

[@SUPACHAWALK]

4 years ago? Somethings might be outdated already.

[@thewhitefalcon8539]

video ID: Lmao, QQQ, it's 4 Q

[@gustiandika1517]

yes IE6 suckss!!!

[@manjumamatabehera6395]

Multiple consumer can not consume from the same partition

[@VictorMartinez-zf6dt]

Make KSQL for Go or I am not using it.