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!
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! 😊
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?
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.
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?
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.
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?
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/
That is very clear introduction to this Data ingestion related process !!!! Love it
This is a very great explanation of difference betweeen queues, event buses and streams. Nice work!
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!
I appreciate you taking the time to comment, thank you ❤️
Excellent breakdown. Thanks James.
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! 😊
Glad you enjoyed it :-)
Best explanation i ’ve seen on this topic. Clear, to the point and well understood. Great work. Looking forward to seeing more. 🎉
Glad you enjoyed it ☺️
Another excellent vid - thanks James 🙂
Excellent video
Good stuff 🎉
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?
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.
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?
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.
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?
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/
@@serverlessjames Thanks for the reply, James. As usual, your answers are detailed and simple to understand.
Thanks for the explanation! What kind of application or pad are you using for drawings ?
It's a Huion drawing tablet on my desk, and then the EpicPen Pro app for the ability to draw on the screen
@@serverlessjamesnice didn’t know that you can stream it like that looks pretty good! 👍
@@serverlessjames is it like a pad or this display like iPad?
@@sergeykichuk2586 yeah it's basically an external display but specifically for drawing on. Google Huion Kamvas 13 :)
@@serverlessjames didn’t know something like that exists always I have issue to draw with mouse! Thank you!
So...where do you put a tool like kafka? Stream maybe?
Yep, that's where I would put it. It sits in that middle ground where it's durable, but also allows for multiple consumers