i'm french and i look your videos it's very cool continue like that , just look books of marketing and personnal devlopment for grow your buisness thank you =) ,
I kind of feel like the mediator you are describing is a SOA ESB pattern and not for microservices. Microservices architecture specifies dumb pipes and smart endpoints. A mediator with logic in between services sounds like the opposite, smart pipes, i.e. the messaging middleware from SOA. Only way a mediator could be applied in microservices by definition would be if each service had one to distribute the event among its internal components.
Very useful content and explained very well... my only feedback can be about your reading flow. It would be better if you stop and wait at some point. Sometimes it's hard to follow since you keep moving without any interval. Thanks a lot.
I'm left with a few questions... When events are handled by a microservice are they generally removed from the queue? What if you wanted more than one type of Microservice to respond to an event? Would the handler event need to send out a new EventHandledEvent? Or would they issue a command? If everything is event driven then where do commands fit in?
Every subsriber of your event system will receive an exact "copy" of the event. So if you have 5 Microservices hooked to the message queue and 3 of them have a listener for lets say userNameChanged, they will all receive said event.
@@zebcode depends on if you are working with acknowledgements or not. There are many possible implementations of a broker & message queue. One is where the broker knows which services have which events subscribed and one where he doesnt. Typically the first one is the case when you are working with acknowledgements. The latter one will just publish the message and "not care" if they ever get received. So if your service had an outage it will have missed a message. TL;DR; It really depends on the implementation that you are using.
Great series! Thank you very much could you please recommend me some useful resources and books regarding software architecture and architecture patterns? I am considering writting my bachelor thesis on something in this direction. Any recommendations? That would be very helpful ^^
Not the best design pattern video I've seen. 1. you didn't give accurate reasons why request-response (RR) is inferior to event bus (EB). Automation can be done with both patterns. The producer of the event might as well use RR to notify all interested parties. It doesn't have to be manual. 2. Unit testing is actually easier for an EB system, as you can test each event publish/handle in isolation It was otherwise OK. Most of the other content was accurate.
Great presentation of the EDA concept. Really love it. Thank you!
Thank you for posting such good content!
You have a great sense of humor ..
great video, ty so much
great content. thanks for the explanation. looking forward to your next video
What a great video! Thank you for sharing your knowledge.
Thank you. Your explanations rock!
Wow! Great explanation, great series, great channel. Thank you very, very much !!!
Very in depth explanation .. Thank you
awesome video, I've learned A LOT!
3:13 oh yes this one in particular would come in very handy now
Really great video
Great content! Very helpful
Nice Presentation
i'm french and i look your videos it's very cool continue like that , just look books of marketing and personnal devlopment for grow your buisness thank you =) ,
Thanks!
I kind of feel like the mediator you are describing is a SOA ESB pattern and not for microservices. Microservices architecture specifies dumb pipes and smart endpoints. A mediator with logic in between services sounds like the opposite, smart pipes, i.e. the messaging middleware from SOA. Only way a mediator could be applied in microservices by definition would be if each service had one to distribute the event among its internal components.
Very useful content and explained very well... my only feedback can be about your reading flow. It would be better if you stop and wait at some point. Sometimes it's hard to follow since you keep moving without any interval. Thanks a lot.
Thank you!
Event driven Architecture is a big pub/sub pattern in cloud. As the complexity increases more support structures like mediators come in play. Period.
I'm left with a few questions...
When events are handled by a microservice are they generally removed from the queue?
What if you wanted more than one type of Microservice to respond to an event?
Would the handler event need to send out a new EventHandledEvent? Or would they issue a command?
If everything is event driven then where do commands fit in?
Every subsriber of your event system will receive an exact "copy" of the event. So if you have 5 Microservices hooked to the message queue and 3 of them have a listener for lets say userNameChanged, they will all receive said event.
@@derNoaa270 ah I see so does the message bus will take care of all subscribers getting the message before removing it?
@@zebcode depends on if you are working with acknowledgements or not. There are many possible implementations of a broker & message queue. One is where the broker knows which services have which events subscribed and one where he doesnt. Typically the first one is the case when you are working with acknowledgements. The latter one will just publish the message and "not care" if they ever get received. So if your service had an outage it will have missed a message.
TL;DR;
It really depends on the implementation that you are using.
👍🏻Great content! Where else could I get myself into EDA?
Thanks a lot for the video!! Vey much appreciated. Some questions have raised. Does anyone know a good book about System Architecture?
Is there is a way that you can give me a quick comparison between Microkernel and event driven ?
Will you be making the slides available?
I ask the same :(
Great series! Thank you very much
could you please recommend me some useful resources and books regarding software architecture and architecture patterns?
I am considering writting my bachelor thesis on something in this direction. Any recommendations? That would be very helpful ^^
is this approach suitable for game non stateful services like leaderboard , profile and stats etc
Hey bro, can u give me the Sources of this video ?
TCP vs UDP?
Not the best design pattern video I've seen.
1. you didn't give accurate reasons why request-response (RR) is inferior to event bus (EB). Automation can be done with both patterns. The producer of the event might as well use RR to notify all interested parties. It doesn't have to be manual.
2. Unit testing is actually easier for an EB system, as you can test each event publish/handle in isolation
It was otherwise OK. Most of the other content was accurate.
Are robots really gonna take over the world ?😅