@danser_theplayer01

With this need for efficiency web development architecture becomes more and more reminiscent of hardware architecture.
This idea of just throwing any signals out there and expecting every different service to handle or pass them differently on their own reminds me of something like cpu architecture.

@rohanofelvenpower5566

visual are so quality you would think the channel has millions of subscribers

@pradeepr2044

You don't know how greafull I am, I absolutely love the content and shared it to all my close friends. Your content is soo good I want them to make use of it too...

@WijthaGayan

Fantastic video! For those looking to explore further, the Akka Actor library and the actor model are excellent topics to dive into for a deeper understanding

@aethermass

Good video. For those wanting to dive deeper, the Akka Actor library and the actor model are good topics to read up on.

@tarunstv796

I have following question, please bear with me for the basic/stupid ones -
1. How to decide on EDA vs Syncronous communication?
2. When a single event can trigger multiple services and they react to it differently then how their reactions are captured? For example - uber example - for ride request - price calculation service, matching service etc. will do their respective jobs but 'who' and 'how' will aggregate all this for uber's customer?
3.  Event Processing: Simple and Complex - How are multiple events aggregated as they can arrive at different times and can change (event1: high demand, event2: rain, event3: low demand, event4: sunny weather)

@parashar1505

wow! what software do you use to make these graphics? it is just so great!

@akhilrafftar6011

I love the way you present your knowledge
in such a simple words with good visualisation

@muhammedadel9673

NATS is also one of those new event distribution channels that's being adopted recently in Netflix and it is open source

@GauravPal-pd9rf

Nicely elaborated, appreciate your efforts.

@rakeshranjan5071

Amazing explanation.  And great animation

@sketchionic6356

Very good explanation.

@ЦзинКэ-ы5х

I think you should've also mentioned that any element in the system (depending on how the MQ is handled, what broker is used, etc, but still) can be both consumer and producer. By the way, aren't "publisher" and "subscriber" equal to producer and consumer at 6:58?

@malliktest9160

I like your diagrams and animation. Which tool are you using?

@manojmaximum

top notch content, animation, voice

@bensdevjourney7081

What animation software do you use? Great video 👍

@softwareengineer8923

Such a useful content, thanks a lot

@vikasvk9174

Very informative video.. Thanks

@Wheretearfalls

Amazing explanation but if possible then try to implement all these patterns using microservices so that we can see realtime usecases that how we can use them in realtime applications like uber and netflix and etc

@sahilq312

Great explanation .