1. Intro to Streams | Apache Kafka® Streams API

MORE ON STREAMS


ABOUT CONFLUENT

#streamprocessing #kafkastreams #kafka #apachekafka

[jasonfeingold]

What a well done presentation. Great delivery of the spoken word. No fluff, good inflection, smooth stream of phonemes. So refreshing, so rare. Good content, too.

[OlleDencker]

I must say, this is a really good presentation. This not a beginners Kafka tutorial, but a Kafka stream tutorial, so in order to get something out of this you should be a bit comfortable with Kafka.

[BymiJonesJunior]

I have watched some videos where a hairy guy makes a presentation of a scala technology. Usually it goes 40-90 minutes. And it's not too easy to get what he means. And when you get what he meant, you realize that there was not too much information. But it takes your time and effort to understand the stuff.
This video is short. The speech is pretty easy to understand and there is no anything redundant. That's really qualitative stuff. Like and subscribe. Good job

[arielmeloful]

More than such a great tool. I just regret that RocksDBjni has no port for AIX / Solaris

[jeffg]

so, is streams api only for Java clients? How about .net, rust, python, etc?

[yonatandaniyel]

If you are a .Net dev is there any way to utilize Streams API?

[Hotpocketmountiandew]

This must be how I sound to people when I talk about martial arts.

[danfr]

"You really want all your code to stay in one place. You don't want to say 'hey, this is my stream processing code, let me make this build and I'll deploy it over here. This is my "application" code, and I'll have all my cool automation deploy this automatically [...] over there. You don't want to break that up. We've done that a number of times[...] And it's always worked out kind of badly."

I have a Node.js application, there's no Java in the mix anywhere. But Streams seems to be Java-only and it sounds like I would have to write a second "Application" for anything I would want to do stream processing; not be able to deploy it as part of the same "application". In addition of course to having to re-implement any utilities my application uses but I also need in the stream processing since they're different languages.


Am I missing something? Cause it feels like the language limitation is self-defeating the desire to not have separate "application" and stream-processing code with separate deployment simply by having nothing in common with the language/build setup you may be using for your "application".

[popboyan]

Confusing.. Didn't say the most important thing. Stream API is used to process messages from one topic and put filtered or transformed ones to another topic.

[scholzj]

Content wise a great video. But visually, Tim's face constantly moving between left and right corner when the slide was on screen was quite annoying and distracting.

[AjaySingh-xdnz]

Must watch!! Those who have disliked this video should also provide justification for disliking.

[bbhanu]

This is what it sounds like when you hire a marketing guy to explain technology.. his upbeat energy is unsettling

[sanjaycharles]

Did you guys hire a music video editor to get this video done..?

[kidzre]

Great content .Thank you, but the presenter jumping around the screen was distracting and quite annoying.

[mrbananaman]

A clear introduction should really include a simple use case and what the topic does at a high level, generalized sense. Think flowchart with very basic data examples.

The only person that would have gotten something from this info already knows what streams is and does.

[syogamurthy]

why the presenter keeps moving. please keep him at a constant position

[UnnaipolOruvan]

anyone following his video series ... you cant learn anything ... he is marketing guru for confluent... he can answer for "WHAT" ... he cant answer for "HOW" & "WHY". Learn open source Kafka ...then learn confluent Kafka.