Comments by "" (@brownhorsesoftware3605) on "Event Driven Architecture EXPLAINED in 15 Minutes" video.

In this case you simply implement an event that is generated when the state is as A is interested in. Then A just registers a listener for that event. NO POLLING! Polling is the opposite of event driven.
4
@andreaszetterstrom7418 Event structure requires thought like anything else. You need to create a rational model to have a comprehensible result.
3
@stengrafflarsen You can define a listener that receives any or all or n of any set of events you wish to implement. There is no limit to how the interactions behave. It depends on the use case. A push client can handle any number of events.
1
Anyone who has spent time closer to the metal knows that computers are event-driven beasts. Heck, msdos was invoked as an x86 interrupt. And it goes way farther back and deeper than that. XEROX PARC etc.
1
Use a queue.
1
Everything on a phone is event-driven. I think that fact and the complete absence of msft are why I like to work in that space so much. This comes up against a strong bias amongst developers favoring the command model. My experience on Android is their urge to 'simplify' things by hiding event interaction in the platform. All that does is add cycles and create thread production mayhem. I don't know this because I use these features, I know this by observing what gets deprecated. By taking advantage of the event architecture, I have never had a performance problem.
1