Event-Driven Architecture: Explained in 7 Minutes!
ฝัง
- เผยแพร่เมื่อ 22 พ.ค. 2024
- Event-driven architecture is an essential architectural pattern used with microservices. In this video, I cover what it is, when you should use it and the pros and cons.
☕️ I don’t accept paid sponsorships and I have turned off mid-video ads. You’re welcome! If you would like to support my channel see: ko-fi.com/alexhyett
📨 Join my free weekly newsletter for advice, technology and more: newsletter.alexhyett.com
🗺️ Backend Developer Roadmap: www.alexhyett.com/backend-dev...
📝 Related blog post: www.alexhyett.com/event-drive...
🎓 RECOMMENDED COURSES (Use code FRIENDS10 for 10% off)
The Complete Web Developer Course - academy.zerotomastery.io/a/af...
The Complete Junior to Senior Web Developer Roadmap - academy.zerotomastery.io/a/af...
Complete SQL + Databases Bootcamp - academy.zerotomastery.io/a/af...
📚 RECOMMENDED BOOKS
Clean Code - geni.us/5AEwj2
Domain Driven Design - geni.us/WiR0Q0x
Design Patterns - geni.us/5ncUt
Developer Hegemony - geni.us/lAXy
Pragmatic Programmer - geni.us/GfNj9
Data Structures and Algorithms Made Easy - geni.us/sqg6kJ
Refactoring - geni.us/ufAP0mE
Pragmatic Thinking and Learning - geni.us/x81A
Microservices - geni.us/8vMA
🚀 MY FAVOURITE TOOLS
PIA VPN - piavpn.com/AlexHyett (86% off)
Visual Studio Code - code.visualstudio.com/
Obsidian - obsidian.md/
Notion - affiliate.notion.so/alexhyett
⏳ TIMESTAMPS
00:00 - What is Event Driven Architecture?
02:24 - When to use it?
03:12 - Advantages
04:41 - Disadvantages
You can check out more of my favourite tools on my website:
www.alexhyett.com/tech/
🔗 MY KEY LINKS
🌍 Blog - www.alexhyett.com/
🐘 Mastodon - social.alexhyett.com/@alex
🧑💻 WHO AM I
I’m Alex, a Software Developer and TH-cam working in the UK. I make videos about software development to help developers with the skills they need to be senior developers. As well as this TH-cam Channel, I also write articles on my website (alexhyett.com) as well as write a regular newsletter that contains some thoughts to help aspiring developers.
‼️ DISCLAIMERS
Some of the links in this description are affiliate links, for which I get a small commission, at no extra cost to you 🙂. I appreciate you supporting my channel so I can continue providing you with free software development content!
#coding #programming #developer - วิทยาศาสตร์และเทคโนโลยี
i am so happy to easy this. because i am a self learning software developer. thanks a looot!!!!
keep going!
thank you very much for covering so many aspects... so well.
Amazing videos man, keep them coming. Thanks!
Hi! Nice explanation! I appreciate the balanced approach to discussing the pros and cons of event-driven architecture. It's important to consider both sides before making a decision, especially eventual consistency, and this video did a great job of laying that out!
Thank you! I am glad you enjoyed it!
Great explanation, thank you !
Feels like the observer pattern but through a network.
Good and very detailed explanation.
Great video!
I love this explanation.. Great guy
Thank you for this amazing video
Great video.
Thank you for the amazing explanation
Glad it was helpful!
Hi Alex, your videos are precise, short and informative. I am loving it and watching it, however on this specific video, wouldn’t it be great to provide more comparative aspect between messages and event based architecture along with more used cases for each?
Thank you! Yes, I will make sure I do some videos on that in the future. I didn't want to cram too much in my first video on the topic.
thank you!
Wow this is the easiest explainer of event driven architecture I've seen! Thank you so much. I used to work with WCF and MSMQ and I feel it's kinda the same except for the fact there's no broker that pushes the events to consumers. I'm kinda curious what the event message looks like in the event driven architecture way of things.
You're very welcome! The event messages can vary quite depending on who is implementing them. Some prefer small messages that just mention that an event occurred. This therefore requires the consumer to call the producer to get more information. Others create quite detailed events that contain all the information that a user would need.
As a producer, it can be a bit of a balancing act between having to constantly add new information to an event which is likely also available via API or having consumers also call your API for every event that comes in.
@@alexhyettdev thank you so much for detailing that! The fun in there is choosing what approach to take then. Might need more experience to find out what kind of event messages to send (from very verbose to just a request to have them poll from the producer the related info)
It mostly comes down to performance. If you need to process hundreds or thousands of events a second you don't want to have to go off to an API to get more information.
A brief dive into queue-based vs log-based would help to make this more complete (eg rabbitmq vs kafka)
Sure I will add it to the list and I can do a video on that in the future.
Very clear thank you! +1 subscriber! :)
Thank you, I am glad it was useful.
Hello, great video. I am fairly new to this, would you use EDA for this use case:
due to Regulatory reasons the company needs to forward emails to certain recipients in the event of an agree-upon trigger. I am sorry if the question is too specific. keep up the good work.
Thanks. Yes, that is quite specific and a difficult one to answer without knowing the system in detail. In theory, you could raise an EmailSent event but you would still need to read the message for the trigger word and then forward it.
Great video! One questing about 3:53: Wouldn't you have the same kind of reliability if you installed a broker between the two services in an event driven architecture, as this would introduce asynchronous execution?
Yes if reliability is your only concern then an event broker would work too. Event-driven architecture does tend to change how you view the architecture of your whole application.
On an "API driven architecture", you have consistency problems too.
When a microservice calls another microservice, they aren't bound to the same transaction (unless using 2PC).
Futhermore, it's hard to manage rollbacks in case of rest call failure.
The structure can become really fragile easily.
Yes they both have consistency problems. I am not sure anyone has come up with a way around that without causing scaling problems.
@@alexhyettdev There is no solution on distributed environnements (CAP theorem)
can you suppress that background barking kind of sound that emits from your laptop when you are running thru the slides
Great tutorial! One important question -- Is there any difference between Event Driven Architecture and Reactive Programming?
Not really, reactive programming is generally implemented using an event based system.
i couldnt understand 1:22-1:30, can you please elaborate on that?
Won't broker in event driven architecture is similar to Orchestrator ?
An orchestrator handles everything including the communication back to the parent service. The event broker on the other hand just passes events along for services that are subscribed. Orchestration is pretty much the opposite of event driven architecture.
You could decrease the background music
Great content! But this sound effect every time when slide appears is suuuuuuper annoying...
Same
Noted!
Keep up the good work! @@alexhyettdev
I like it actually
I didn’t start feeling annoyed until you said that 😅
Nice video, really liked it, but I get the feeling you dragged "eventual consistency" kicking and screaming into your example of services being slow to pick up events. It probably doesn't belong there, as that term is more about data consistency between different databases ... even though it could be related in some scenarios I guess.
Haha I love the analogy. Yes it definitely depends on the scenario. A lot of the time when I have used EDA is where I have had reporting systems fed from it hence it coming up.
What if a subscriber can't keep up with the events produced by the producer?
It is just a case of scaling up the number of subscribers. Of course, this can have its own limitations. There might be a bottleneck downstream that caps how many events you can process. This is especially true if each of those subscribers is writing to the same database. This is where you need to start looking at things such as database sharding or caching all the reads.
@@alexhyettdev Thanks, great video by the way!
@@user-mx8ij4tk6i Thanks!
I like the explanation but one thing that i so much wanted but it seems lacking in the video is showing us how it's done or where it's used in real life applications, this is what makes the video relatable not just telling us the advantages and disadvantages. How do I know ad and disadv when i don't even know how it works in a real life application
Great video tho
I am not sure if that emoji is pointing upwards or giving me the finger 🤣. I hope it’s the former!