Such a great explanation - vey clear that you really know what you're talking about. A quick question - you said that in the API messaging archtiecture that the ecommerce system could reach a failure in trying to retry messaging an unavailable service. Is this a concern with a event router service - what prevents it form also becoming overwhelmed with retry failures?
Most systems have options to handle this. 1. You can set the retries for a max time and also exponential back off so there is a waiting period before retrying 2. There is something called dead lettering that will take the failed messages after they hit the max and send them somewhere else (of your design). Like a log or a different service.
Similar concepts. I think reactive programming starts to get into a more of a programming pattern instead of an architecture of multiple systems working together but all the concepts are the same
Maybe we can differentiate 2 semantics when talking about reactive, one is purely development technic which consists in using the streams of data. Another is architectural style, you can get somr glimps if you search for Reactive Manifesto. Here, imho, it is very same as event driven arch.
Hi there! Your videos are super helpful :) What do you think is the best approach to gain hands-on experience with architecture design and implementation? I am currently studying towards the AWS Certified Architect Associate Exam, but I just don't want to earn the certification and learn the theory. I want to actually implement stuff. Thanks your time and content.
Hello and thank you for the comment. In my career, I was able to do the best hands-on learning by working in the devops and continuous delivery automation space. I think that automating the deployments of systems provides a ton of knowledge on how things work and where they don’t work. Building out systems with something like terraform is a good place to start or really any other infrastructure provisioning tool for that matter. Obviously terraform is more universal but if you are going for aws specifically they also have similar tools designed to bring up entire sets of cloud tools which will help you understand how they work and how they work together.
Thanks for the feedback. The background music volume is hard to get exactly right because it sounds way different depending on what type of speakers you have.
@@emonymph6911 Not really, I prefer some music in the background. As long as it isn't too loud and it was pretty low in this video (I have big studio headphones on). But each to their own.
@@yega3k why don't you put on your own background music playlist then. You never want to bake the music track into the 'how to' tutorial... if people want music they can listen to it themselves we're not disabled.
@@emonymph6911 I wouldn't go through that much trouble just to watch a quick 6 minute RUclips video that popped up in my feed. If this were a longer video (30 min to 2 hours) then I'd agree with you. For a quick video, some music is totally fine imo.
i think from a purely technical standpoint they are separate things, but in terms of event driven architecture any system that builds a relationship between event publishers and systems that reacts to events could be substituted for a router. one that comes to mind for me is a marketing tool call Tealium EventStream. This tool receives events that happen on a website, then evaluates the event and compares to a users profile attributes then decides which subscribers should receive the event based on the rules you create. This would not be considered strictly an event router but still falls into event-driven architecture.
Short and sweet - to the point. Thank you brother
Glad it was helpful!
Man, thanks so much for this simple explanation. You got skills in effective communication.
Thanks! Glad you liked it!
really good job, this deserves more views
Nice video, thanks!
Glad you liked it!
Such a great explanation - vey clear that you really know what you're talking about. A quick question - you said that in the API messaging archtiecture that the ecommerce system could reach a failure in trying to retry messaging an unavailable service. Is this a concern with a event router service - what prevents it form also becoming overwhelmed with retry failures?
Most systems have options to handle this.
1. You can set the retries for a max time and also exponential back off so there is a waiting period before retrying
2. There is something called dead lettering that will take the failed messages after they hit the max and send them somewhere else (of your design). Like a log or a different service.
Super useful tutorial! One important question -- Is there any difference between Event Driven Architecture and Reactive Programming?
Similar concepts. I think reactive programming starts to get into a more of a programming pattern instead of an architecture of multiple systems working together but all the concepts are the same
Maybe we can differentiate 2 semantics when talking about reactive, one is purely development technic which consists in using the streams of data. Another is architectural style, you can get somr glimps if you search for Reactive Manifesto. Here, imho, it is very same as event driven arch.
@@MykhayloS make sense and very well explained!!
Hi there!
Your videos are super helpful :)
What do you think is the best approach to gain hands-on experience with architecture design and implementation?
I am currently studying towards the AWS Certified Architect Associate Exam, but I just don't want to earn the certification and learn the theory. I want to actually implement stuff.
Thanks your time and content.
Hello and thank you for the comment.
In my career, I was able to do the best hands-on learning by working in the devops and continuous delivery automation space.
I think that automating the deployments of systems provides a ton of knowledge on how things work and where they don’t work.
Building out systems with something like terraform is a good place to start or really any other infrastructure provisioning tool for that matter.
Obviously terraform is more universal but if you are going for aws specifically they also have similar tools designed to bring up entire sets of cloud tools which will help you understand how they work and how they work together.
good info but you have some sort of music in the background that is so low its almost inaudible but i found it super distracting.
Thanks for the feedback. The background music volume is hard to get exactly right because it sounds way different depending on what type of speakers you have.
@@LearnFastMakeThings background music is always a bad idea idk why people think it's good. the video itself was nice though thanks for sharing.
@@emonymph6911 Not really, I prefer some music in the background. As long as it isn't too loud and it was pretty low in this video (I have big studio headphones on). But each to their own.
@@yega3k why don't you put on your own background music playlist then. You never want to bake the music track into the 'how to' tutorial... if people want music they can listen to it themselves we're not disabled.
@@emonymph6911 I wouldn't go through that much trouble just to watch a quick 6 minute RUclips video that popped up in my feed. If this were a longer video (30 min to 2 hours) then I'd agree with you. For a quick video, some music is totally fine imo.
Can event router be a orchestrator ?
i think from a purely technical standpoint they are separate things, but in terms of event driven architecture any system that builds a relationship between event publishers and systems that reacts to events could be substituted for a router.
one that comes to mind for me is a marketing tool call Tealium EventStream. This tool receives events that happen on a website, then evaluates the event and compares to a users profile attributes then decides which subscribers should receive the event based on the rules you create.
This would not be considered strictly an event router but still falls into event-driven architecture.