Thanks a million James. I agree with the other commenter that this is the best explanation on this topic. You have an outstanding ability to explain complex subjects in a way that is easy to follow. I'm very lucky to have found your channel!
@serverlessjames7 ай бұрын
I appreciate you taking the time to comment, thank you ❤️
@tangomoocow12 күн бұрын
Great explanation, thanks.
@irisll42602 ай бұрын
That is very clear introduction to this Data ingestion related process !!!! Love it
@antonmartyniuk4 ай бұрын
This is a very great explanation of difference betweeen queues, event buses and streams. Nice work!
@josef-stampede-ai7 ай бұрын
Best explanation i ’ve seen on this topic. Clear, to the point and well understood. Great work. Looking forward to seeing more. 🎉
@serverlessjames7 ай бұрын
Glad you enjoyed it ☺️
@adeyemialatishe826 ай бұрын
Excellent breakdown. Thanks James.
@carlcodes84227 ай бұрын
Another excellent vid - thanks James 🙂
@runek754 ай бұрын
Excellent description of these technologies! It really gave insight into what to use when. Thanks for the tip and your talk at the ndc in oslo, really inspiring! 😊
@serverlessjames4 ай бұрын
Glad you enjoyed it :-)
@johncerpa37827 ай бұрын
Excellent video
@RichardBaileyrichoncode9 күн бұрын
Was hoping to see more about latency comparisons.
@selmanekici88167 ай бұрын
Good stuff 🎉
@sumarianprince7 ай бұрын
Great video as usual James, thanks for this. I have a side question for you, I made a wager with my colleague that c# AOT 8.0 is superior to NodeJS's Latest version on AWS in terms of performance. Who do you think wins?
@serverlessjames7 ай бұрын
I'd be confident .NET 8 Native AOT will be more performant, simply because it's a natively compiled binary as opposed to node which is an interpreted language. Max's Lambda perf benchmarks seem to back that up, if you're talking pure performance. maxday.github.io/lambda-perf/
@sumarianprince7 ай бұрын
@@serverlessjames Thanks for the reply, James. As usual, your answers are detailed and simple to understand.
@bulioh5 ай бұрын
Very clear breakdown! When using an event bus (not combined with a queue), does every instance of a consumer receive a message typically? Or is it load balanced to a single instance?
@serverlessjames5 ай бұрын
Great question. Typically an event bus is there to fan a single event out to lots of different subscribers. So yeah, if you had multiple instances of the same app subscribed directly to the bus with the same configuration I'd expect them all to receive the same events.
@bradgermain6 ай бұрын
Thanks James, this is great! Quick question, you mentioned for a stream it’s important that a DB is setup on both services, is that the case for queues and service buses too?
@serverlessjames6 ай бұрын
Yes, absolutely. Basically you don't want to be relying on your message channel as a persistent data store. Many streams will retain data for period of time, but they aren't databases.
@sergeykichuk25866 ай бұрын
Thanks for the explanation! What kind of application or pad are you using for drawings ?
@serverlessjames6 ай бұрын
It's a Huion drawing tablet on my desk, and then the EpicPen Pro app for the ability to draw on the screen
@sergeykichuk25866 ай бұрын
@@serverlessjamesnice didn’t know that you can stream it like that looks pretty good! 👍
@sergeykichuk25866 ай бұрын
@@serverlessjames is it like a pad or this display like iPad?
@serverlessjames6 ай бұрын
@@sergeykichuk2586 yeah it's basically an external display but specifically for drawing on. Google Huion Kamvas 13 :)
@sergeykichuk25866 ай бұрын
@@serverlessjames didn’t know something like that exists always I have issue to draw with mouse! Thank you!
@Namelessssssssssssssss7 ай бұрын
So...where do you put a tool like kafka? Stream maybe?
@serverlessjames7 ай бұрын
Yep, that's where I would put it. It sits in that middle ground where it's durable, but also allows for multiple consumers