Nice intro about .net development with Kafka! Yes, I'd like more videos with more scenarios - along with implementation details - in which Kafka proves itself very handy. Thank you!
Thank you for your video. A Kafka series sounds like a fantastic idea. It could delve into Kafka's functionalities, illustrating what it's capable of and how users can leverage it effectively.
Hi saeed, thanks for great explanation with short duration. I want to ask, how if the consumer fails saving data because maybe there's any field required(consumer side) but the not provided by producer.
Good question, the Consumer needs to tell kafka to commit the message, either auto-commit by kafka lib or manually commit by developer, the point is you need to handle the validation on consumer so if there is a invalid message you just skip that message and commit it without processing.
This video was very helpful, but is there any chance you know why I get the error " Connect to ipv4#127.0.0.1:9092 failed: Unknown error (after 2032ms in state CONNECT)" with both the producer and consumer? Thanks!
Thank you and happy it was helpful. About the error, please follow the code in my repo the link is in the description, better to use localhost:9092 and make sure both Kafka and zookeeper are using same network.
@@cvetomiranedelcheva9946 Are you run kafka and zookeeper both? they have access to call each other? I think better to run in docker to make sure the problem is not in your code
Well the idea behind them are different, first one Kafka is 'designed' for highly scalability which means is suitable for millions of events per seconds but RabbitMQ not, Second one RabbitMQ will remove messages from queue once consumer commit it but Kafka retains the messages until amount of time (default 7 days) so that you can read the event again if you need. And many other differences, their concept came for solving different problems
Nice intro about .net development with Kafka! Yes, I'd like more videos with more scenarios - along with implementation details - in which Kafka proves itself very handy. Thank you!
Appreciate for the feedback and sure I'll create more videos on this topic
Thank you for your video. A Kafka series sounds like a fantastic idea. It could delve into Kafka's functionalities, illustrating what it's capable of and how users can leverage it effectively.
Totally agree, Kafka is highly customizable and needs to understand the configuration and tune it based on usecases.
Hi! It was nice tutorial. I want to learn about sink connector for Kafka. Thank you!
Hi saeed, thanks for great explanation with short duration.
I want to ask, how if the consumer fails saving data because maybe there's any field required(consumer side) but the not provided by producer.
Good question, the Consumer needs to tell kafka to commit the message, either auto-commit by kafka lib or manually commit by developer, the point is you need to handle the validation on consumer so if there is a invalid message you just skip that message and commit it without processing.
❤❤❤❤❤❤❤❤❤❤❤
Thanks:)
This video was very helpful, but is there any chance you know why I get the error " Connect to ipv4#127.0.0.1:9092 failed: Unknown error (after 2032ms in state CONNECT)" with both the producer and consumer? Thanks!
Thank you and happy it was helpful.
About the error, please follow the code in my repo the link is in the description, better to use localhost:9092 and make sure both Kafka and zookeeper are using same network.
@@sa-es-ir But that's what I'm doing. Is it possible that my error comes from not using docker?
@@cvetomiranedelcheva9946 Are you run kafka and zookeeper both? they have access to call each other?
I think better to run in docker to make sure the problem is not in your code
@@sa-es-ir Okay, thank you very much!!
Hi it was nice tutorial and really helpful, However, I want to learn more about sink connect for Kafka.. Thank you!
Great suggestion! I put it in the list
Hi, great video!
What is the advantage to use Kafka over rabbitMQ?
Well the idea behind them are different, first one Kafka is 'designed' for highly scalability which means is suitable for millions of events per seconds but RabbitMQ not,
Second one RabbitMQ will remove messages from queue once consumer commit it but Kafka retains the messages until amount of time (default 7 days) so that you can read the event again if you need.
And many other differences, their concept came for solving different problems