Came to see a high-level benchmark of two important technologies, but ended up learning some really interesting facts about production Kafka. I've been searching for that exact info on Kafka with/without Kubernetes for a while - thank you for covering it!
One is a messaging protocol the other one is a message broker. Comparing these two with each other is like comparing your car with your carpet. But I guess buzz words are good for the views.
What would be better for media streaming between microservices? I'm leaning towards gRPC considering a lot of "chunks" needs to be transferred per second per user. I dont need a request response but low latency is a must. Also, using gRPC avoids any scaling needs of kafka in the future as the user base grows Is my understanding correct, Anton? Isnt this a ideal usecase where a comparison between grpc and kafka is suitable?
Hmmm… Both of these technologies are different types of IPC. I’m confused. I think comparisons between REST and gRPC or RabbitMQ and Kafka are more correct
How are you going to realize producer - consumers and something like garatied delivery and handle call/message, with grpc only? Ok for if for the first you just use load balancer, grpc calls from one producer can automatically stick to some consumer after the first call and after do not balance (this behavior I saw 2 years ago with grpc in kubernetes, sometimes it is ok) Interesting to compare Kafka vs RabbitMQ vs other Message systems in terms of latency...
Thanks for the feedback. They are not compatible most of the time. But I saw people choose Kafka when they just are better off with simple grpc. I'll test different messaging systems as you suggested.
🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - me@antonputra.com
Came to see a high-level benchmark of two important technologies, but ended up learning some really interesting facts about production Kafka. I've been searching for that exact info on Kafka with/without Kubernetes for a while - thank you for covering it!
Latest Kafka versions does not require Zookeeper anymore
it's not production ready
In 3.3.1 release notes it says KRaft is prod ready 🤔
One is a messaging protocol the other one is a message broker. Comparing these two with each other is like comparing your car with your carpet. But I guess buzz words are good for the views.
I wish, it's based on my personal experience at my current company
Someone explain me how are these two competing technologies?
They are not, but I know someone who should've picked grpc instead =)
What would be better for media streaming between microservices?
I'm leaning towards gRPC considering a lot of "chunks" needs to be transferred per second per user. I dont need a request response but low latency is a must. Also, using gRPC avoids any scaling needs of kafka in the future as the user base grows
Is my understanding correct, Anton?
Isnt this a ideal usecase where a comparison between grpc and kafka is suitable?
yes, if low latency is important, try to use grpc, there are other protocols available, but for your use case i think it's the best
One has nothing to do with the other. Wtf?
most of the time
Exactly my reaction, lol.
It's like asking: "Which color should a painter use when making a painting, blue or green?".
Hmmm… Both of these technologies are different types of IPC. I’m confused. I think comparisons between REST and gRPC or RabbitMQ and Kafka are more correct
Do NATs vs. [whatever]! It will be a good serie and alternative to Kafka (burn it alive)
yeah, nats streaming
How are you going to realize producer - consumers and something like garatied delivery and handle call/message, with grpc only? Ok for if for the first you just use load balancer, grpc calls from one producer can automatically stick to some consumer after the first call and after do not balance (this behavior I saw 2 years ago with grpc in kubernetes, sometimes it is ok)
Interesting to compare Kafka vs RabbitMQ vs other Message systems in terms of latency...
Thanks for the feedback. They are not compatible most of the time. But I saw people choose Kafka when they just are better off with simple grpc. I'll test different messaging systems as you suggested.
which one should we use to create a chat application which handles millions of messages per second?
cassandra?
cassandra is a database, this comment makes absolutely no sense, same as the video
grpc golang can act as a producer and consumer, isn't is? Kafka as a broker? Am I wrong? I have started learning this just now.
well, you can create golang producers and consumers and use RPC messages, same as in gRPC, but it's a different concept altotherher
message queue is better because its asynchonous
and slower
For sake of your overall channel content, you would like to delete this invalid comparison. Just a suggestion..
It's maybe obvious to you, but some don't realize that. It is a thing =)
Partitions not partisions please correct your slides
thanks, too late