Video není dostupné.
Omlouváme se.
Event Driven Architecture | System Design
Vložit
- čas přidán 17. 09. 2020
- The video kicks off with defining EDA as a "software architectural style" used in complex distributed system. It then explains how in a distributed environment like Microservices requests get routed with the help of central node to independent services.
This Model wherein api request is used as a trigger is know as Request Driven Model.
Further a possible scenario where one of the services fail and the request is terminated abruptly is discussed and how in RDA it is very difficult to revert back to the previous state.
A detailed discussion of what are events, how they are created and read by Publisher Subscriber Model. We then discuss how EDA with the help of events has solved the reverting problem.
EDA has humongous applications in gaming industry in games like PubG or racing games where respawn is a very common feature.
Happy Learning!
#EventDrivenArchitecture #SystemDesign
I really appreciate the contribution of India Tech Guys, thanks from Vietnam
I absolutely love the way you explain!
A touch of Hindi always helps me understand better :)
@Finnegan Arthur How is that related to "Event Driven Architecture" in any way?
I hope, he didn't say anything essential in those moments. I was really confused because I thought, I hadn't just understood what he said and listened again and again till I realised that had been Hindi :D
@@dmitrikonnov922 I am sure you won't face any issues. His english explanation was thorough enough!
The diagrams of the presentation are very helpful to understand the EDA. I got the points of the advantages of EDA now. I will refactor my architecture using EDA. Thanks man, explained the idea to me.
Great explanation, I tried other videos too to understand EDA but your way is much simpler and understandable. Looking forward to a video to implement this in the sample code.
Keep up the good work !!!
This is one the best explanations of the event driven architecture I've come across so far!
If you think this is the best explanation, then I feel surprised it only gained a handful of likes 👍
man, you have very unique ability to share the information clearly and simply, keep going, never stop this knowledge sharing habit
Finally a good channel talking about system design
Shakul mate my most useful 15 mins on EDA ever. Awesome thank you so much
Thank you so much for this wonderful overview. Very underrated channel. Subscribed!
still don't know how to reverse when failed
Great explanation - I'm new to EDA and wondered how it was different to conventional systems. Thanks
Really easy explanation and comparison with Request - Response system
Well done Shakul . You explain the base of systems , core of architecture . Expecting more videos from you
It's very helpful. Keep it up your good work & efforts and one thing more, thanks.
You made it very simple for us...great help...thank you
Great explanation. Thanks!
Thank you brother! Very good explanation...
Man you explained it amazingly need to binge you channel now😆
Now i can imagine how easily scalable these systems can be 🤔
Great explanation, after watching many videos, this one made the concepts much clear, thanks shakul
Good Explaination!
Explanation is great. Loved it. Subscribing to ur channel bro.
very good explaination.
@10:32 will UI directly put the event to the event hub, I was thinking it should come via router?
very clear
Nicely explained 👌👏
Top Notch Content!!
Very Helpful
Nice explanation. Keep it up.
Do you have coding example of how the message object is design so that can fit to the dynamic request body and also the response. Like general wrapper for all the requests and responses.
Super examples
To make this work shouldn't UI also register with the Event Hub, what if we have many different clients all need to be registered?
What are the commercial products for Request Response Architecture and EDA ? Nice explanation.
By the time service got failed, updateDB service would have committed the data in updated db table. can we rollback the data once its committed in the updated db table?
niceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee, botiful, understanable, clear, effictive, thnkooooo sir for your hadd work it rallly help me
Hindi/English combo is good👍 Refer to your example. In EDA, how are rollback of multiple microservices tied together - is there a 'transaction id' as a 'Key' field (or data ekement) in all atomic / individual messages that constitute a single transaction in the event hub (say Kafka)? Who orchestrates or keeps track of 'linking the pieces' together?
I laughed so hard when he started to explain it in hindi
Nice explanations 👏👏. How does it the response goes to the UI. Is it same like request-driven for this case ?
And please put you picture with white board on that video icon
Personally I feel people tend to be more attracted to a with board setup than ppt kind of lecture. I initially thought it would be a ppt explanation 😅
Loved the way you explain!
Nice Explanation! shakul...I have one doubt here..as you said publisher puts message in event bus....any subscriber can take the message from there...so where is security constraint there in pub sub model.
Great explanation. Can you share some sample code!
🤙
A touch of hindi superb to understand
I’m slowly learning a foreign language…
I like your explanation but keep in mind not all of us understand your language
not everyone knows hindi, it creates confusion for those who doesn't
I believe the material is at least perfect but sometimes I can not understand any word and any sentence ............